SAP for Automotive Discussions
Connect with fellow SAP users in discussions to troubleshoot challenges, share best practices, and fuel each other's success. Join a conversation or start your own.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

JIT call handling within the same SAP system

Former Member

‎06-14-2012 8:38 PM

0 Kudos

Hallo

We have a scenario wherein the OEM and Tier 1 supplier are using the same SAP system and want to interact using JIT calls. Any idea how this can be implemented.

Is there a need to have 2 JIT calls, one outbound  (created at OEM for KANBAN with purchase Scheduling agreement) and another with same data (inbound for Tier 1 to hit a SD Scheduling agreement )

OR

the same JIT call can be used at both ends since they are in the same SAP system.

Any inputs would be highly appreciated.

4 REPLIES 4

Former Member

‎06-19-2012 11:24 AM

0 Kudos

Hi,

Only one JIT call with reference to a scheduling agreement is involved (usually one scheduling agreement per material). The OEM trigger the JIT call based on the assembly sequence of a vehicle. This JIT call can be forwarded to the Tier 1 Supplier via EDI, Supplier Collaboration or SRM. This JIT call will trigger the replenishment process at the supplier side. This assumes that the OEM and the Supplier are using separate SAP system.

Your supplier and your OEM share the same SAP ECC system but with a different company code?

John

Former Member
In response to Former Member

‎06-19-2012 5:09 PM

0 Kudos

Hi John

The OEM and supplier have different company codes.

Since supplier and OEM are in same SAP system, is there a possibility, that the outbound JIT call (on OEM side) can be converted to an inbound JIT call (Supplier side) without the involvement of middleware. This will drive business advantage and avoid middleware related costs.

Former Member
In response to Former Member

‎06-20-2012 6:43 AM

0 Kudos

Hi,

In your case, you definitely don't need to use a middleware, not even an IDoc. My recommendation to you is to investigate the use of the following BAdI in ECC:

  1. Control Items During Release Creation
  2. Release Creation for Scheduling Agreements with Release Documentation

John

tomasz_domanski
Contributor

‎06-11-2013 7:10 AM

0 Kudos

You may consider inter Company Code stock transfer (with or without billing depending on what are your legal requirements). Then you do not really need any JiT calls as the Scheduling Agreement is automatically visible in both Company Codes (e.g. for MRP). MRP / Kanban / other sources create & change schedule lines. The supplier just creates Outbound Deliveries on specific day.

You can find more info in SAP help e.g. http://help.sap.com/saphelp_46c/helpdata/en/dd/5614f4545a11d1a7020000e829fd11/content.htm