JIT Processing with the Next-Generation Just-in-Time in S/4HANA- Part 2 -

[meher_souayeh]

JIT Master Data and EDI Configuration

As outlined in the first part, a prerequisite to build a summarized JIT Call processing scenario in S/4HANA is first to run the classical order-to-cash scenario “Sales from stock” utilizing a customer and a material master data. In addition to these essential master data, the following configurations and settings will be required to run the JIT scenario:

1. Assign the required roles to configure and run the JIT processes in Fiori
2. Maintain the unloading point and the EDI identification of the ship-to
3. Sold-to party determination and EDI configuration in SD
4. Maintain customer JIT master data
5. Maintain JIT Customer Supply Controls     
6. Create sales schedule agreement with type “LZJ”
7. Configure the webservices for the Delivery Forecast Schedule (DELFOR) and JIT Call (DELJIT) in  SOAMANAGER.

1. Assign the required roles to configure and run JIT processes in Fiori:

Process	Role	Tile group/Tiles
Manage JIT Master Data	SAP_BR_MD_SPECIALIST_JIT	JIT/JIS supply-to-customer master data(*): · Manage JIT Customer Data · Manage JIT Customer Supply Controls · Manage Packing Group Specification
Monitor EDI Messages	SAP_BR_CONF_EXPERT_BUS _NET_INT	Message Monitoring: · Message Monitoring AIF · Message Monitoring Overview · Assign Recipients to Users · Message Dashboard
Sales processes:	SAP_BR_INTERNAL_SALES_REP	Sales Scheduling Agreement: · Manage Sales Scheduling Agreement · Analyze and Copy Scheduling Agreement Sales Scheduling Agreement Master Data: · Manage Delivery Schedule Processing · Assign Sold-to Parties · Manage Deviation Profile

(*) Only the tiles “Manage JIT Customer Data” and “Manage JIT Customer Supply Controls” will be used in this demo. The other tiles are needed primarily for the Just-in-Sequence scenario (sequenced JIT Calls).

2. Maintain the unloading point and EDI identification of the ship-to party

• Customer unloading point is a key entity in automotive and it specifies the location at which the material is to be unloaded. For this demo, we will use the unloading point “UNLOAD001” and maintain it the business partner master data. 

                              

• The EDI identification, WRK1, of the receiving plant will be maintained in the business partner master data as “Partner Description” of the Ship-to Party:

3. Sold-to party determination and EDI configuration in SD

To enable EDI communication between the buyer’s and the seller’s systems, a mapping between the business data of both parties, such ship-to number, vendor number, and plant code is necessary. This mapping is done in the following configurations:

• Assign sold-to parties: When transmitting the JIT call, the buyer will send the following data:

• Vendor number of the seller in his system, for example BUYER001
• The plant code to which the materials must be shipped, for example WRK1
• The unloading point where the materials must be unloaded, for example UNLOAD001.

This transmitted information will be used in the seller’s system to uniquely identify a sold-to party. The assignment is done through the app “Assign Sold-to Parties”.

 

• Sales EDI Conversion – VOE4 – : Maintain the sold-to party in the column "customer" and the ship-to party in the column "internal partner number". In the column "Partner function" enter "SH: ship-to".

• Sales EDI Customer/Supplier – VOE2 – : Maintain the Ship-to partner number in the column customer

4. Maintain Customer JIT Data

Utilize the Fiori app “Manage JIT Customer Data” to flag the customer as relevant for the JIT processing and maintain the key parameters for the JIT Processing such as the destinations, the external status mapping, the additional reference types, the delivery control, and the JIT call processing control.

For the basic scenario of summarized JIT calls processing in this demo, we maintained the following JIT parameters for the customer OEMSMJ001:

• Destination: CSA_SUM001/UNLOAD001/LOC001
• External Status Mapping: NEW (receive new JIT call) /MOD (Modify existing call)/ CANC (Cancel created call)
• Delivery Control: No Split

 If you have maintained consistently the customer JIT master data as described in points 3 and 4, the customer should appear in the cds view “I_JITSALESAREAPARTNERDATA” when accessed via SE16N.

5. Maintain JIT Customer Supply Controls

Utilize the Fiori app “Manage JIT Customer Supply Controls” to maintain the JIT control data specific to the customer. For the basic scenario of summarized JIT calls processing in this demo, we maintained the following JIT control parameters for the customer OEMSMJ001:

 Action Control: S2C_SUMC (control profile delivered as part of the standard SAP)

Delivery Confirmation Control: no (in this demo we won’t use customer consignment process).

Partial Delivery Allowed: Yes (in this demo, we allow delivery creation with partial quantity).

6. Create JIT Sales Scheduling Agreement

Create Sales Scheduling Agreement with the document type “LZJ: JIT Scheduling Agt-” using the app “Create Sales Scheduling Agreements (VA31)”

 

Verify that the “Unloading Point” is copied correctly from the business partner master data to the shipping view of the sales scheduling agreement item.

 Verify that the EDI identification of the partner “WRK1” is copied correctly to the partner view of the sales scheduling agreement.

7. Maintain the interfaces for the processing of the incoming EDI messages

 Using the transaction “SOAMANAGER”, you can configure the interface to receive the EDI messages for the Forecast Delivery Schedule and the JIT Call.

In this blog we are not going into details how to use the “Web Service Configuration”. For these activities you can get some guidances from the blog post SOAMANAGER CONFIGURATION. 

For our demo, we have configured the following interfaces:

1. SCHEDAGRMTDLIVSCHEDULE_IN
2. JITCALLREQUEST_IN

To validate if the services are correctly configured, you can use the transaction SCIF and test the access:  

After maintaining these JIT and EDI configurations, you will be able process summarized JIT Call  using the next-generation Just-in-Time in S/4HANA. In the upcoming blog post, Part 3 of this series, we will demonstrate how to run the end-to-end scenario of processing summarized JIT Call using the nJIT solution, from receiving the EDI message for the delivery forecast to invoicing of the delivered goods.