AutoEdge
EHP4 for SAP ERP
6.0
March 2011
English
Scheduling
Agreement
with Summarized JIT Call
(A67)
Business Process Documentation
SPARTA
A KPIT Cummins Company
Corporate Headquarters
111 Woodmere Road Suite 200
Folsom, CA 95630
888-985-0301
916-985-0300
AutoEdge
Scheduling Agreement With Summarize JIT Call (127): BPD
Contents
1
Purpose ......................................................................................................................................... 3
2
Prerequisites.................................................................................................................................. 4
2.1
Master Data and Organizational Data .................................................................................... 4
2.2
Business Conditions ............................................................................................................... 5
2.3
Roles ...................................................................................................................................... 5
3
Process Overview Table ............................................................................................................... 6
4
Process Steps ............................................................................................................................... 8
5
4.1
OEM Processes: Planned Independent Requirements Processing ...................................... 8
4.2
OEM Processes: Material Requirements Planning ................................................................ 9
4.3
OEM Processes: Displaying the Schedule Lines in the Scheduling Agreements ............... 11
4.4
OEM Process: Creating Scheduling Agreement Release ................................................... 11
4.5
OEM Process: Displaying the Releases from the Scheduling Agreements ........................ 13
4.6
OEM Process: Message Outputting: Delivery Schedules .................................................... 14
4.7
OEM Process: EDI Outbound Processing, Forecast Delivery Schedule ............................. 15
4.8
Supplier Process: EDI Inbound Processing, Forecast Delivery Schedule ........................... 16
4.9
Supplier Process: Processing Forecast Delivery Schedule for Scheduling Agreement ...... 17
4.10
OEM Process: Material Staging – Summarized JIT Call .................................................. 18
4.11
OEM Process: Changing/Displaying the Summarized JIT Call........................................ 19
4.12
OEM Process: Sending an Outbound Summarized JIT Call............................................ 20
4.13
Supplier Process: SD Determination of the Incoming Summarized JIT Call ................... 21
4.14
Supplier Process: Calling Monitoring for the Inbound Summarized JIT Calls .................. 22
4.15
Supplier Process: Delivery the Summarized JIT Call ....................................................... 23
4.16
Supplier Process: Posting Good Issue ............................................................................. 24
4.17
Supplier Process: Billing the Outbound Delivery / Summarized JIT Call ......................... 25
4.18
OEM Process: Posting GR for outbound JIT call ............................................................. 26
4.19
OEM Process: Completing / Deleting the Outbound JIT Call........................................... 27
Close Action ................................................................................................................................ 28
5.1
OEM Process: Reverse Stock.............................................................................................. 28
5.2
OEM Process: Reverse Independent Requirements Processing ........................................ 29
5.3
OEM Process: Material Requirements Planning.................................................................. 30
©2011 Sparta Consulting
Page 2 of 31
AutoEdge
Scheduling Agreement With Summarize JIT Call (127): BPD
Scheduling Agreement with Summarized JIT Call
1
Purpose
General Information and Target User
This documentation gives an instruction on how the scenario: (A67 – Scheduling Agreement with
Summarized JIT Call) is processed from business point of view, Also, it gives a step by step
operation guide, which the users can follow to finish the process of this scenario.
The target user of this documentation will possibly be:

Partners

Customers
Overview
The incoming summarized JIT call inbound receives calls whose items comprise a date and quantity
pair. The items are not linked to the finished product and are not delivered in a predefined sequence.
The call reference number controls downstream processes, such as the delivery creation or the
transport creation.
This type of processing can be employed when the manufacturer transfers calls for non-vehicle
related materials. Call components (= materials ordered via releases) are often pre-produced and
the summarized JIT calls can be delivered immediately after the goods have been received. The call
components are documented in the delivery Comment and in the subsequent invoice. The R/3
System contains a material master for each call component.
In general, the following scenarios are supported:

Calls for individual materials:
In a summarized JIT call, the manufacturer sends one or more quantities and dates for a call
component. The system stores the summarized JIT call reference number as an external call
number in the call header (the external reference number is stored in the summarized JIT call at
header level). This scenario can be used for mapping PSA / NISSAN / RENAULT KANBAN
calls.

Calls for multiple materials:
In a summarized JIT call, the manufacturer sends multiple materials for a summarized JIT call
number and date. The system stores each material as a call component and stores the
reference number as an external call number (the external reference number is stored in the
summarized JIT call at item level). This scenario can be used for mapping the OPEL MAIS pick
up sheet.
Note
This form of sales order processing is essentially different from mapping the
summarized JIT calls as JIT calls (that is, importing a summarized JIT call as a JIT
call) in two ways:
The manufacturer does not transfer any cumulative quantities or a “final delivery
number”. In the same way various information about the summarized JIT call is sent,
such as a KANBAN number (in variant 2 this is the outbound summarized JIT call
number), point of consumption, and so on. This information must be stored in the JIT
call at schedule line level (no fields are available for this in the JIT call).
This process description focuses on the “calls for individual materials” scenario.
©2011 Sparta Consulting
Page 3 of 31
AutoEdge
Scheduling Agreement With Summarize JIT Call (127): BPD

Creating an outbound summarized JIT call

Creating a summarized JIT call in inbound processing

Delivering the summarized JIT call

Billing the summarized JIT call delivery
The manufacturer uses forecast delivery schedules to transfer a rough estimate of the quantities
required.
The summarized JIT call transfers a refined outbound forecast and a delivery release.
This occurs when the manufacturer:

2
Sends a manually created outbound summarized JIT call to the supplier via EDI. The supplier
supplies the data from the summarized JIT call accordingly and bills the services he has
performed.
Prerequisites
2.1 Master Data and Organizational Data
Default Values
Essential master and organizational data was created in your ERP system during the
implementation phase, such as the data that reflects the organizational structure of your company
and master data that suits its operational focus, for example, master data for materials, vendors, and
customers.
The business process is enabled with this organization-specific master data, examples of which are
provided in the next section.
Use the following master data in the process steps described in this document:
Master / Org. Data
Value
Master / Org. Data Details
Material
A-67-2000_OEM
Air Condition Type A
Plant
1000
Vendor
A-V6701
A production plant
Vendor A-V6701
OEM Client Master data:
MM Scheduling Agreement 560006701
Supplier Client Master data:
Material
A-67-2000_SUP
Air Condition Type A
Sold-to party:
A-6701
Customer
A-6701
Customer A-6701
Customer A-6701
Sales organization:
1000
Dom. Sales Org
Distribution Channel
10
Direct Sales
Division
10
Product Division 10
Plant
1000
Storage Location
1040
A production plant
Shipment w / o LWM
©2011 Sparta Consulting
Page 4 of 31
Comments
AutoEdge
Scheduling Agreement With Summarize JIT Call (127): BPD
2.2 Business Conditions
The business process described in this Business Process Documentation is part of a bigger chain of
integrated business processes or scenarios. As a consequence, you must have completed the
following processes and fulfilled the following business conditions before you can start going through
this scenario:
Business Condition
Scenario
You have completed all relevant steps described in the Business
Process Documentation Prereq. Process Steps (154).
Prereq. Process Steps
(154)
2.3 Roles
Use
The following roles must have been installed to test this scenario in the SAP NetWeaver Business
Client (NWBC).You only need these roles if you are using the NWBC interface. You do not need
these roles if you are using the standard SAP GUI
Prerequisites
The business roles have been assigned to the user who is testing this scenario for OEM Client.
Business Role
Technical Name
Process Step
Employee
(Professional User)
SAP_NBPR_EMPLOYEE-S
Assignment of this role is necessary
for basic functionality.
Strategic Planner
SAP_NBPR_STRATPLANNERS
OEM Processes: Planned
Independent Requirements
Processing
Production Planner
SAP_NBPR_PRODPLANNER-S OEM Processes: Material
Requirements Planning
Purchaser
SAP_NBPR_PURCHASER-S
OEM Processes: Displaying the
Schedule Lines in the Scheduling
Agreements
OEM Process: Creating Scheduling
Agreement Release
OEM Process: Message Outputting:
Delivery Schedules
IT Administrator
(Professional User)
SAP_NBPR_IT_ADMIN-S
OEM Process: EDI Outbound
Processing, Forecast Delivery
Schedule
Production Planner
(AUTO)
SAP_NBPR_PRODPLANNER_
AUTO-S
OEM Process: Material Staging –
Summarized JIT
Logistics Execution
JIT (AUTO)
SAP_NBPR_JIT_AUTO-S
OEM Process: Changing/Displaying
the Summarized JIT Call
OEM Process: Sending an Outbound
Summarized JIT Call
OEM Process: Posting GR for
©2011 Sparta Consulting
Page 5 of 31
AutoEdge
Scheduling Agreement With Summarize JIT Call (127): BPD
Business Role
Technical Name
Process Step
outbound JIT call
OEM Process: Completing / Deleting
the Outbound JIT call
The business roles have been assigned to the user who is testing this scenario for Supplier Client.
Business Role
Technical Name
Process Step
Employee
(Professional User)
SAP_NBPR_EMPLOYEE-S
Assignment of this role is necessary
for basic functionality.
IT Administrator
(Professional User)
SAP_NBPR_IT_ADMIN-S
Supplier Process: EDI Inbound
Processing, Forecast Delivery
Schedule
Sales Administrator
SAP_NBPR_SALESPERSON-S
Supplier Process: Processing
Forecast Delivery Schedule for
Scheduling Agreement
Logistics Execution
JIT (AUTO)
SAP_NBPR_JIT_AUTO-S
Supplier Process: SD Determination
of the Incoming Summarized JIT Call
Supplier Process: Calling Monitoring
for the Inbound Summarized JIT Calls
Supplier Process: Delivery the
Summarized JIT Call
Warehouse Clerk
SAP_NBPR_WAREHOUSECLE
RK-S
Billing Administrator SAP_NBPR_BILLING-S
3
Supplier Process: Posting Good Issue
Supplier Process: Billing the
Outbound Delivery / Summarized JIT
Call
Process Overview Table
Process Step
Business
role
Transaction
Code
Expected
Results
OEM Processes:
Planned
Independent
Requirements
Processing
Strategic
Planner
MD61
OEM Side:
Planned
Independent
Requirements
Created
OEM Processes:
Material
Requirements
Planning
Production
Planner
MD02
MRP run
OEM Processes:
Displaying the
Schedule Lines in
the Scheduling
Agreements
Purchaser
ME39
Displaying the
Schedule Lines
©2011 Sparta Consulting
External
Process
Reference
Business
Condition
Page 6 of 31
AutoEdge
Scheduling Agreement With Summarize JIT Call (127): BPD
Process Step
Business
role
Transaction
Code
Expected
Results
OEM Process:
Creating Scheduling
Agreement Release
Purchaser
ME84
Created
Scheduling
Agreement
Release
OEM Processes:
Displaying the
Schedule Lines in
the Scheduling
Agreements
Purchaser
ME39
Displaying the
Schedule Lines
OEM Process:
Message Outputting:
Delivery Schedules
Purchaser
ME9E
Delivery
Schedules
Message is
Output
OEM Process: EDI
Outbound
Processing,
Forecast Delivery
Schedule
IT
Administrator
(Professional
User)
WE05
EDI Outbound
display
Supplier Process:
EDI Inbound
Processing,
Forecast Delivery
Schedule
IT
Administrator
(Professional
User)
WE05
EDI Iutbound
display
Supplier Process:
Processing Forecast
Delivery Schedule
for Scheduling
Agreement
Sales
Administrator
VA33
Display the
forecast delivery
schedule
OEM Process:
Material Staging –
Summarized JIT
Production
Planner
(AUTO)
PK23
summarized
JIT call has
been
generated
OEM Process:
Changing/Displaying
the Summarized JIT
Call
Logistics
Execution JIT
(AUTO)
PJ03
Displaying the
Summarized
JIT Call
OEM Process:
Sending an
Outbound
Summarized JIT Call
Logistics
Execution JIT
(AUTO)
JITOM
an outbound
summarized
JIT call is send
to the supplier
Supplier Process:
SD Determination of
the Incoming
Summarized JIT Call
Logistics
Execution JIT
(AUTO)
EMJIT
check the
IDOC received
from customer
Supplier Process:
Calling Monitoring
for the Inbound
Summarized JIT
Logistics
Execution JIT
(AUTO)
JIT3
summarized
JIT call with
the external
©2011 Sparta Consulting
External
Process
Reference
Business
Condition
Page 7 of 31
AutoEdge
Scheduling Agreement With Summarize JIT Call (127): BPD
Process Step
External
Process
Reference
Business
Condition
Business
role
Transaction
Code
Calls
Expected
Results
number display
Supplier Process:
Delivery the
Summarized JIT Call
Logistics
Execution JIT
(AUTO)
JITK
a delivery is
created for the
summarized
JIT call
Supplier Process:
Posting Good Issue
Warehouse
Clerk
VL02N
a delivery is
posted for the
summarized
JIT call
Supplier Process:
Billing the Outbound
Delivery /
Summarized JIT Call
Billing
Administrator
VF04
billing is
carried out
OEM Process:
Posting GR for
outbound JIT call
Logistics
Execution JIT
(AUTO)
JITOM
OEM post
goods receipt
for outbound
JIT call.
OEM Process:
Completing /
Deleting the
Outbound JIT call
Logistics
Execution JIT
(AUTO)
JITOM
OEM finishes
the processing
of outbound
JIT call
4
Process Steps
4.1 OEM Processes: Planned Independent Requirements
Processing
Use
PIRs (Planned Independent Requirements) is created in this step. This step will reflect on MRP run
and generate schedule lines.
Procedure
1. Access the activity using one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Production  Production Planning  Demand
Management  Planned Independent Requirements  Create
Transaction code
MD61
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
©2011 Sparta Consulting
Strategic Planner
Page 8 of 31
AutoEdge
Scheduling Agreement With Summarize JIT Call (127): BPD
(SAP_NBPR_STRATPLANNER-S)
Business role menu
Production  Production Planning  Demand Management 
Create Planned Indep. Requirements
2. On the Create Planned Independent Requirements: Initial Screen, make the following entries:
Field name
Description
User action and values
Comment
Material
A-67-2000_OEM
Change the planned
independent requirements for
each material
Plant
1000
Version
00
Planning period
M
3. Choose User Parameters,
4. On the Settings: User Parameters pop-up screen, make the following entry:
Field name
Description
User action and values
Comment
VSF
Requirements type
5. Choose Enter to confirm your entries.
6. Choose Continue (Enter) in the Information dialog box to confirm the save of user parameters.
7. On the Create Planned Independent Requirements: Initial Screen, choose Enter.
8. Choose Sched.lines tab page.
9. On the Plnd ind.reqmts Create: Schedule Lines screen, make the following entry:
Field name
Description
User action and values
Comment
ReqmtDate.
Next month
For example, 12.2010
Planned qty
200
10. Choose Save.
11. Choose Back (F3) to return to the SAP Easy Access screen (SAP GUI).
Or
Choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP
Home (SAP NetWeaver Business Client).
4.2 OEM Processes: Material Requirements Planning
Use
In this step, we run MRP to generate schedule line.
Prerequisites
©2011 Sparta Consulting
Page 9 of 31
AutoEdge
Scheduling Agreement With Summarize JIT Call (127): BPD
The vendor A-V6701 is stored in the source list as a fixed vendor for materials A-67-2000_OEM and
therefore, material requirements planning generate schedule lines automatically.
Procedure
1. Access the activity using one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Production  MRP  Planning  Multilevel Single-Item
Planning
Transaction code
MD02
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Production Planner
(SAP_NBPR_PRODPLANNER-S)
Business role menu
Production  MRP  Planning  MRP - Single-Item, Multi-Level
2. On the Single Item Multi Level screen, make the following entries:
Field name
Description
User action and values
Material
A-67-2000_OEM
Plant
1000
Comment
MRP control
parameters
Processing key
NETCH
Create purchase req.
2 (Purchase requisitions in opening
period)
Delivery Schedules
3 (Schedule lines)
Create MRP list
1 (MRP list)
Planning mode
1 (Adapt planning data (normal
mode))
Scheduling
1 (Basic dates will be determined for
planned orders)
3. Confirm your entries by choosing Enter twice.
Note
The system displays an overview of the statistics generated and informs you that
planning has been carried out.
4. Choose Back (F3) to return to the SAP Easy Access screen (SAP GUI).
Or
Choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP
Home (SAP NetWeaver Business Client).
©2011 Sparta Consulting
Page 10 of 31
AutoEdge
Scheduling Agreement With Summarize JIT Call (127): BPD
4.3 OEM Processes: Displaying the Schedule Lines in the
Scheduling Agreements
Use
In this step, we check whether the schedule line is generated automatically after MRP run.
Procedure
1. Access the activity using one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Materials Management  Purchasing  Outline
Agreement  Scheduling Agreement  Delivery Schedule 
Display
Transaction code
ME39
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Purchaser
(SAP_NBPR_PURCHASER-S)
Business role menu
Purchasing  Outline Agreement  Scheduling Agreement 
Display Sched. Agmt Schedule
2. On the Display Sch. Agmt. Schedule: Initial Screen, make the following entries:
Field name
Agreement
Description
User action and values
Comment
5600006701
3. Choose Enter.
4. On the Display Sch. Agmt. Schedule: Item Overview screen, select Item 10, and choose from
menu (NWBC: More…) Item  Delivery schedule.
Note
Here, you can see the schedule lines in the individual outline agreements that were
generated by the MRP planning run.
5. Choose Back (F3) to return to the SAP Easy Access screen (SAP GUI).
Or
Choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP
Home (SAP NetWeaver Business Client).
4.4 OEM Process: Creating Scheduling Agreement
Release
Use
©2011 Sparta Consulting
Page 11 of 31
AutoEdge
Scheduling Agreement With Summarize JIT Call (127): BPD
In this step, delivery schedules are created based on the scheduling agreement delivery schedule
lines and released to the supplier.
Note
The scheduling agreement is assigned a release profile YA02, which sends forecast
delivery schedules to the vendor every week for the next 6 months.
Procedure
1. Access the activity using one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Materials Management  Purchasing  Outline
Agreement  Scheduling Agreement  Create SA Release
Transaction code
ME84
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Purchaser
(SAP_NBPR_PURCHASER-S)
Business role menu
Purchasing  Outline Agreement  Scheduling Agreement
 Generation of Sched. Agmt. Releases
2. On the Create Releases screen, make the following entries:
Field name
Description
User action and values
Comment
 FRC scheds only
Choose release type
Select scheduling
agreements
1000
Plant
MRP area
MRP controller
A-67-2000_OEM
Material
Vendor
Scheduling
agreement
5600006701
Scope of select.
Choose:
Changed or next date
Optional-
 (on)
Optional-
W/o checking
strategy in
profile
Created on
Acc. to strat. in profile
W/o checking
strategy in
profile
©2011 Sparta Consulting
Page 12 of 31
AutoEdge
Scheduling Agreement With Summarize JIT Call (127): BPD
Additional functions
remove 
Test run
3. Choose Execute (F8).
4. On the Create Releases screen, the system then displays the messages together with the
forecast delivery schedule numbers.
5. Choose Back (F3) to return to the SAP Easy Access screen (SAP GUI).
Or
Choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP
Home (SAP NetWeaver Business Client).
4.5 OEM Process: Displaying the Releases from the
Scheduling Agreements
Use
In this step, we check whether the schedule lines are released.
Procedure
1. Access the activity using one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Materials Management  Purchasing  Outline
Agreement  Scheduling Agreement  Delivery Schedule 
Display
Transaction code
ME39
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Purchaser
(SAP_NBPR_PURCHASER-S)
Business role menu
Purchasing  Outline Agreement  Scheduling Agreement 
Display Sched. Agreement Schedule
2. On the Display Sch. Agmt. Schedule: Initial Screen, make the following entries:
Field name
Agreement
Description
User action and values
Comment
5600006701
3. Confirm you inputs with Enter, and choose the first scheduling agreement item.
4. Select the item 10, and choose from menu (NWBC: More…) Item  SA release docu.
Note
Here, you can see the individual outputs that were generated.
5. Choose Back (F3) to return to the SAP Easy Access screen (SAP GUI).
©2011 Sparta Consulting
Page 13 of 31
AutoEdge
Scheduling Agreement With Summarize JIT Call (127): BPD
Or
Choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP
Home (SAP NetWeaver Business Client).
4.6 OEM Process: Message Outputting: Delivery
Schedules
Use
After the messages (delivery schedules) have been generated (see previous step), the created
IDocs need to be sent to the EDI subsystem. In this scenario, the messages are sent to supplier
Side.
Procedure
1. Access the activity using one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Materials Management  Purchasing  Outline
Agreement  Scheduling Agreement  Delivery Schedule
 Print/Transmit
Transaction code
ME9E
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Purchaser
(SAP_NBPR_PURCHASER-S)
Business role menu
Purchasing  Outline Agreement  Scheduling Agreement
 Message Output: Sch. Agmt. Schedules
2. On the Message Output screen, make the following entries:
Field name
Description
User action and values
Comment
Purch. doc. data
Document number
5600006701
Vendor
A-V6701
Only in case of
messages for SA
releases
Plant
1000
Only messages for SA
release
 (choose)
Message data
Application
EL
Message type
©2011 Sparta Consulting
Page 14 of 31
.
AutoEdge
Scheduling Agreement With Summarize JIT Call (127): BPD
Processing status
0
Creation date
Today's date
Time created
3. Choose Execute (F8).
4. The system displays a list containing a number of documents. Select the desired documents
with  at the start of the line.
5. Choose Output message, the forecast delivery schedules are then sent to the vendor via EDI.
6. Choose Back (F3) to return to the SAP Easy Access screen (SAP GUI).
Or
Choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP
Home (SAP NetWeaver Business Client).
4.7 OEM Process: EDI Outbound Processing, Forecast
Delivery Schedule
Use
In this step, we check whether EDI Outbound processing has been carried out successfully. If the
SAP System transfers the IDocs to the EDI subsystem, you can find out the status of the IDocs by
means of a list.
Note
If it is carried out successfully, the IDoc is assigned the status 03.
Procedure
1. Access the activity using one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Materials Management  Product Catalog 
Environment  IDoc Overview
Transaction code
WE05
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
IT Administrator (Professional User)
(SAP_NBPR_IT_ADMIN-S)
Business role menu
IT Administration  Administration  IDocs  IDoc Lists
2. On the IDoc List screen, make the following entries:
Field name
Description
User action and values
Default
Created at
©2011 Sparta Consulting
Page 15 of 31
Comment
AutoEdge
Scheduling Agreement With Summarize JIT Call (127): BPD
Created on
Today
Last changed at
Last changed on
DELFOR
Logical message
Message variant
Message function
Partner port
Partner number
Partner type
Partner role
3. , you see an IDoc with the status 03 (Data Passed to port OK)
4. Choose Back (F3) to return to the SAP Easy Access screen (SAP GUI).
Or
Choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP
Home (SAP NetWeaver Business Client).
4.8 Supplier Process: EDI Inbound Processing, Forecast
Delivery Schedule
Use
In this step, we check whether EDI inbound processing has been carried out successfully. If the EDI
subsystem transfers the IDocs to the R/3 System, you can find out the status of the IDocs by means
of a list.
Note
If scheduling is carried out successfully, the IDoc is assigned the status 53.
Procedure
1. Access the activity using one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Materials Management  Product Catalog 
Environment  IDoc Overview
Transaction code
WE05
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
IT Administrator (Professional User)
(SAP_NBPR_IT_ADMIN-S)
Business role menu
©2011 Sparta Consulting
IT Administration  Administration  IDocs  IDoc Lists
Page 16 of 31
AutoEdge
Scheduling Agreement With Summarize JIT Call (127): BPD
2. On the IDoc List screen, make the following entries:
Field name
Description
User action and values
Comment
Default
Created at
Created on
Last changed at
Last changed on
Logical message
DELFOR
Message variant
Message function
Partner port
Partner number
Partner type
Partner role
3. If posting has been carried out successfully, you see an IDoc with the current status 53
(application document posted).
4. Choose Back (F3) to return to the SAP Easy Access screen (SAP GUI).
Or
Choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP
Home (SAP NetWeaver Business Client).
4.9 Supplier Process: Processing Forecast Delivery
Schedule for Scheduling Agreement
Use
In this step, the supplier receives the forecast delivery schedules via EDI, that is, the
scheduling agreement schedule lines are entered in the SD scheduling agreement.
Note
The vendor receives the delivery schedules via EDI. The cumulative quantities are
updated automatically.
When a new delivery schedule is received, the variance tolerances are checked. When
a new delivery schedule is received, a planned delivery schedule is created
automatically. You can change this planned delivery schedule manually in the
scheduling agreement so that smoothed requirements can be passed on to materials
planning.
Procedure
1. Access the activity using one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
©2011 Sparta Consulting
Page 17 of 31
AutoEdge
Scheduling Agreement With Summarize JIT Call (127): BPD
SAP ECC menu
Logistics  Sales and Distribution  Sales  Scheduling
Agreement  Display
Transaction code
VA33
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Sales Administrator
(SAP_NBPR_SALESPERSON-S)
Business role menu
Sales  Scheduling Agreements  Display Scheduling
Agreement
2. On the Display Scheduling Agreement: Initial Screen, make the following entries.
Field name
Description
Scheduling
Agreement
User action and values
Comment
35006701
Determine the forecast delivery
schedule number with a match
code using the customer's PO
number (for example,
5600006701 for EXT).
3. Choose Enter to confirm your entries.
4. On the Display SchedAgrt w/Dly Ord. 35006701: Overview screen, the system displays the
scheduling agreement header and item data.
5. Select the item 10 and from the menu choose the menu: (NWBC: More…) Goto  Item 
Forecast dlv. sched.
6. Choose Back (F3) to return to the SAP Easy Access screen (SAP GUI).
Or
Choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP
Home (SAP NetWeaver Business Client).
4.10 OEM Process: Material Staging – Summarized JIT
Call
Use
In this step, delivery-relevant calls are sent to the vendor. A summarized JIT call can be
delivered at a specific time (partial-day) or several times a day.
Procedure
1. Access the activity using one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Production  KANBAN  Control  Kanban
Signal  Event-Driven Kanban
Transaction code
PK23
©2011 Sparta Consulting
Page 18 of 31
AutoEdge
Scheduling Agreement With Summarize JIT Call (127): BPD
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Production Planner (AUTO)
(SAP_NBPR_PRODPLANNER_AUTO-S)
Production  Kanban  Control  Manual Kanban Creation
Business role menu
2. On the Create: Kanban screen, make the following entries:
Field name
Description
User action and values
Comment
Material
Activate line indicator ())
A-67-2000_OEM
Plant
1000
Supply area
YA0004
3. Confirm your entries by choosing Enter.
The system proposes data from the control cycle for a new summarized JIT call.
4. Choose Save. Record the Summarized JIT call number __________________.
5. Choose Back (F3) to return to the SAP Easy Access screen (SAP GUI).
Or
Choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP
Home (SAP NetWeaver Business Client).
4.11 OEM Process: Changing/Displaying the Summarized
JIT Call
Use
In this step, you can display the summarized JIT call.
Procedure
1. Access the activity using one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Production  KANBAN  JIT Call  Display
Transaction code
PJ03
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Logistics Execution JIT (AUTO)
(SAP_NBPR_JIT_AUTO-S)
Business role menu
Logistics Execution  JIT Outbound  Display Summarized JIT
Call
2. Enter the JIT call number.
3. Choose Enter to confirm your entry.
©2011 Sparta Consulting
Page 19 of 31
AutoEdge
Scheduling Agreement With Summarize JIT Call (127): BPD
4. On the Summarized JIT Call XXXXXXXXXX screen, you can see the scheduling agreement in
the Purchasing Doc. field.
5. The summarized JIT call has generated an output. To view this output, choose Message F6.
6. Choose Back (F3) to return to the SAP Easy Access screen (SAP GUI).
Or
Choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP
Home (SAP NetWeaver Business Client).
4.12 OEM Process: Sending an Outbound Summarized JIT
Call
Use
In this step, an outbound summarized JIT call is send to the supplier.
Procedure
1. Access the activity using one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Logistics Execution  JIT Outbound  Control Data 
Monitoring JIT Outbound
Transaction code
JITOM
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Logistics Execution JIT (AUTO)
(SAP_NBPR_JIT_AUTO-S)
Business role menu
Logistics Execution  JIT Outbound  Monitoring JIT Outbound
2. On the Monitor for Outgoing Calls screen, make the following entries:
Field name
Description
User action and values
Comment
D
Summarized
JIT call
Header Data for Independent calls
Call type
3. Choose Components Group tab page, make the following entries:
Field name
Description
User action and values
Components Groups Data
Vendor
A-V6701
4. Choose Execute (F8).
5. Select the call at header level that you want to send.
6. Choose Actions. The possible actions are displayed.
©2011 Sparta Consulting
Page 20 of 31
Comment
AutoEdge
Scheduling Agreement With Summarize JIT Call (127): BPD
7. Choose Action OSDD /Send Outbound Call: Process Message
8. Choose Execute Action & Back (F9).
9. Choose Back (F3) to return to the SAP Easy Access screen (SAP GUI).
Or
Choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP
Home (SAP NetWeaver Business Client).
4.13 Supplier Process: SD Determination of the Incoming
Summarized JIT Call
Use
In this step, you check the IDOC received from customer.
Note
The JIT call, triggered by a summarized JIT call outbound, receives an internally
assigned number. The vendor uses this number as an external summarized JIT call
number (for identification purposes). No other internal summarized JIT call numbers are
assigned.
Procedure
1. Access the activity using one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Logistics Execution  JIT Inbound  Environment 
IDoc  IDoc Monitor for JIT Calls
Transaction code
EMJIT
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Logistics Execution JIT (AUTO)
(SAP_NBPR_JIT_AUTO-S)
Business role menu
Logistics Execution  JIT Inbound  IDoc Monitor for JIT Calls
2. On the IDoc Monitor for Incoming JIT Calls screen, confirm the following values:
Field name
Description
User action and values
Created at
Created on
Today's date
SummJIT call
 (choose)
Application do.posted
(status 53)
 (choose)
3. Choose Execute.
©2011 Sparta Consulting
Page 21 of 31
Comment
AutoEdge
Scheduling Agreement With Summarize JIT Call (127): BPD
4. If the time is not specific enough, several IDocs may appear. Choose the most recent IDoc
(Time created), and choose IDoc Display to display the IDoc.
5. Expand the Data Records folder.
6. Double-click the IDoc segment E1KSJCL.
7. The external call number is stored in the PRODN field. Make a note of this number (including
leading zeros). External call number ___________________
8. Choose Back (F3) to return to the SAP Easy Access screen (SAP GUI).
Or
Choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP
Home (SAP NetWeaver Business Client).
4.14 Supplier Process: Calling Monitoring for the Inbound
Summarized JIT Calls
Use
In this step, the IDOC can be displayed.
Note
The inbound IDoc has created a summarized JIT call with the external number (from the
E1KSJCL-PRODN IDoc field).
Procedure
1. Access the activity using one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Logistics Execution  JIT Inbound  JIT Call 
Display
Transaction code
JIT3
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Logistics Execution JIT (AUTO)
(SAP_NBPR_JIT_AUTO-S)
Business role menu
Logistics Execution  JIT Inbound  Display JIT Call
2. On the Display JIT Call screen, make the following value and choose Enter.
Field name
Description
User action and values
Comment
Sold-to party
A-6701
Partner Desc.
1000
It is case sensitive.
Ext. JIT call No.
As noted above
Can also be searched
via matchcode – sold-to
party.
©2011 Sparta Consulting
Page 22 of 31
AutoEdge
Scheduling Agreement With Summarize JIT Call (127): BPD
Maintenance Mode
3. You can find the JIT call details.
4. Choose Back (F3) to return to the SAP Easy Access screen (SAP GUI).
Or
Choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP
Home (SAP NetWeaver Business Client).
4.15 Supplier Process: Delivery the Summarized JIT Call
Use
In this step, a delivery is created for the summarized JIT call. This is only possible with transaction
JITK (summarized JIT calls due for shipment).
Prerequisites
Note
Check the stock using transaction code MMBE.
If sufficient stock is not available for creating the delivery in the following process, you
can post additional stock using the movement type 561.
Procedure
1. Access the activity using one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Logistics Execution  JIT Inbound  Follow-on
Functions  Delivery  Summarized JIT Calls Due for Delivery
Transaction code
JITK
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Logistics Execution JIT (AUTO)
(SAP_NBPR_JIT_AUTO-S)
Business role menu
Logistics Execution  JIT Inbound  Summarized JIT Calls Due
for Dely
2. On the Summarized JIT Call ( JIT Call View) screen, confirm the following values:
Field name
Description
User action and values
Shipping
point/Receiving Pt
1000
Deliv. Creation Date
Today’s date or select a date in
the future.
Ship-to party
A-6701
©2011 Sparta Consulting
Page 23 of 31
Comment
AutoEdge
Scheduling Agreement With Summarize JIT Call (127): BPD
Role
JIT2 must be stored as the role –
with summarized JIT calls.
In User Role tab
page
Customer JITCall
no.
External call number recorded
above (for example:
0000000002)
In Summarized
JIT Call tab page
3. Choose Execute (F8).
4. On the Activities Due for Shipping Summarized JIT calls (JIT call view) screen, choose the
summarized JIT call due for deliver which contains sold-to party A-6701 and material A-672000_SUP.
5. Choose the Create Delivery in Background to create the delivery in the background.
Note
You cannot create the delivery with the “Create single delivery in dialog” pushbutton.
6. Choose menu (NWBC: More…) Goto  Create Delivery Log to check the log details
7. On the Delivery Creation Log screen, choose Documents. You can find the delivery number.
Record the Delivery number ____________________.
8. Choose Back (F3) to return to the SAP Easy Access screen (SAP GUI).
Or
Choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP
Home (SAP NetWeaver Business Client).
4.16 Supplier Process: Posting Good Issue
Use
In this step, a delivery is posted for the summarized JIT call.
Procedure
Option 1: SAP Graphical User Interface (SAP GUI)
1. Access the activity using one of the following navigation options:
SAP ECC menu
Logistics  Sales and Distribution  Shipping and Transportation
 Outbound Delivery  Change  Single Document
Transaction code
VL02N
2. Enter in Outbound Delivery number you recorded and choose Enter.
3. On the Change Outbound Delivery screen, select the item and choose Post goods issue to finish
processing the delivery.
4. Choose Back (F3) to return to the SAP Easy Access screen (SAP GUI).
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
1. Access the transaction choosing one of the following navigation options:
©2011 Sparta Consulting
Page 24 of 31
AutoEdge
Scheduling Agreement With Summarize JIT Call (127): BPD
Business role
Warehouse Clerk
(SAP_NBPR_WAREHOUSECLERK-S))
Warehouse Management  Shipping  Outbound Delivery
Business role menu
2. Select the Due for Post Goods Issue tab page, expand Show Quick Criteria Maintenance.
3. Enter the Shipping Point / Receiving Pt: and choose Apply (refresh the current query if
necessary).
4. Select your Delivery.
5. Choose Goods issue.
6. Choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP
Home (SAP NetWeaver Business Client).
4.17 Supplier Process: Billing the Outbound Delivery /
Summarized JIT Call
Use
In this step, billing is carried out.
Procedure
Option 1: SAP Graphical User Interface (SAP GUI)
1. Access the activity using one of the following navigation options:
SAP ECC menu
Logistics  Sales and Distribution  Billing  Billing Document 
Process Billing Due List
Transaction code
VF04
2. On the Maintain Billing Due List screen, confirm the following values:
Field name
Description
User action and values
Billing date to
Today’s date or select a date
in the future.
Sold-to party
A-6701
Documents to be selected
Delivery-related
Comment
select
3. Choose DisplayBillList. The deliveries to be billed are displayed.
4. Select the delivery and choose Individual billing document. Then the Invoice (F2) create:
Overview of Billing Items screen appears.
5. Choose Save to create the billing document.
6. Choose Back (F3) to return to the SAP Easy Access screen (SAP GUI).
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
©2011 Sparta Consulting
Page 25 of 31
AutoEdge
Scheduling Agreement With Summarize JIT Call (127): BPD
1. Access the transaction choosing one of the following navigation options:
Business role
Billing Administrator
(SAP_NBPR_BILLING-S)
Business role menu
Sales  Billing
2. On the Billing screen choose Billing Due List tab page (refresh the current query if necessary).
3. Expand Show Quick Criteria Maintenance, enter the relevant search criteria; (for example: soldto – party: A-6701) select the Delivery-Related flag. Choose Apply
4. Mark the lines with the sales documents you want to bill then choose Billing in Background.
5. The system provides you with a list of the created billing documents.
6. Choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP
Home (SAP NetWeaver Business Client).
Result
Financial postings:
Posting Key
Account
Description
Amount (example)
Currency
01
A-6701
Customer A-6701
4,410,000
JPY
50
81110000
Revenue - domestic
4,200,000-
JPY
50
42210000
Receipt - cons tax
210,000-
JPY
4.18 OEM Process: Posting GR for outbound JIT call
Use
OEM post goods receipt for outbound JIT call.
Procedure
1. Access the activity using one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Logistics Execution  JIT Outbound  Control Data 
Monitoring JIT Outbound
Transaction code
JITOM
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Logistics Execution JIT (AUTO)
(SAP_NBPR_JIT_AUTO-S)
Business role menu
Logistics Execution  JIT Outbound  Monitoring JIT Outbound
2. On the Monitor for Outgoing Calls screen, make the following entries:
©2011 Sparta Consulting
Page 26 of 31
AutoEdge
Scheduling Agreement With Summarize JIT Call (127): BPD
Field name
Description
User action and values
Comment
D
Summarized JIT call
Header Data for Independent calls
Call type
3. Choose Components Group tab page, make the following entries:
Field name
Description
User action and values
Comment
Components Groups Data
Vendor
A-V6701
4. Choose Execute (F8).
5. Select the call at header level that you want to send.
6. Choose Actions. The possible actions are displayed.
7. Choose Action OGRE /Post Goods Receipt for JIT Outbound.
8. Choose Execute Action & Back (F9).
Note
You can check the GR material document through menu (NWBC: More... ) Goto 
Components Group  Material Documents. If you can not find the material document,
you can exit the transaction JITOM and access it again.
9. Choose Back. You go to the screen List of Selected Outbound Calls.
Note
Do not leave the transaction for further processing.
4.19 OEM Process: Completing / Deleting the Outbound
JIT Call
Use
OEM finishes the processing of outbound JIT call.
Procedure
1. Without leaving previous screen, on the List of Selected Outbound Calls screen, choose Actions.
The possible actions are displayed.
2. Choose Action OFIN / Complete Outbound Components Group.
3. Choose Execute Action & Back (F9).
4. Confirm the appearing message “Action OFIN Complete Outbound Components Group was
executed successfully 1 times”.
5. Choose Actions again.
6. Choose Action OREO / Delete JIT Outbound Calls.
©2011 Sparta Consulting
Page 27 of 31
AutoEdge
Scheduling Agreement With Summarize JIT Call (127): BPD
7. Choose Execute Action & Back (F9).
8. Choose Yes to confirm Data deletion
9. Confirm the appearing message.
10. Choose Refresh.
11. The outbound JIT call is deleted and no longer displayed.
12. Choose Back (F3) to return to the SAP Easy Access screen (SAP GUI).
Or
Choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP
Home (SAP NetWeaver Business Client).
5
Close Action
You have finished all the activities that are part of the business process described in this document.
To repeat this business process, carry out the process steps described in the followings:
5.1 OEM Process: Reverse Stock
Use
The purpose of this activity is to reverse stock.
Procedure
1. Access the activity using one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Materials Management  Inventory Management 
Goods Movement  Goods Movement (MIGO)
Transaction code
MIGO
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Warehouse Clerk
(SAP_NBPR_WAREHOUSECLERK-S)
Business role menu
Warehouse Management  Consumption and Transfers  Other
Goods Movement
2. On the Goods Receipt Other screen, choose A01 Goods Receipt R10 other, then choose Enter.
3. Enter following entries:
Field name
Description
User action and values
Material
A-67-2000_OEM
Qutantity
For example:10
©2011 Sparta Consulting
Page 28 of 31
Comment
Use MMBE review
the stock, reverse all
AutoEdge
Scheduling Agreement With Summarize JIT Call (127): BPD
unrestricted stocks
Movement Type
562
Plant
1000
Storage Location
1040
4. Choose Enter.
5. Choose Save.
6. Choose Back (F3) to return to the SAP Easy Access screen (SAP GUI).
Or
Choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP
Home (SAP NetWeaver Business Client).
5.2 OEM Process: Reverse Independent Requirements
Processing
Use
This business process step is used to delete planned independent requirements of a purchased part
at the customer side.
Procedure
1. Access the activity using one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Production  Production Planning  Demand
Management  Planned Independent Requirements  Change
Transaction code
MD62
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Strategic Planner
(SAP_NBPR_STRATPLANNER-S)
Business role menu
Production  Production Planning  Demand Management 
Change Planned Indep. Requirements
2. On the Change Planned Independent Requirements: Initial Screen, maintain in accordance with
the following table:
Field name
Description
User action and values
A-67-2000_OEM
Material
MRP area
1000
Plant
Selection
parameters
©2011 Sparta Consulting
Page 29 of 31
Comment
AutoEdge
Scheduling Agreement With Summarize JIT Call (127): BPD
Version
Activate all active versions
- or Selected version (00)
 (on)
- or all active/inactive
versions
Planning
horizon
From
If necessary, change value
defaulted by system
To
If necessary, change value
defaulted by system
Planning
period
M
Monthly
3. Confirm your entries and the message output by the system.
4. On the Plnd ind. reqmts Create: Planning Table screen, delete all the independent requirements.
5. Choose Save.
6. Choose Back (F3) to return to the SAP Easy Access screen (SAP GUI).
Or
Choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP
Home (SAP NetWeaver Business Client).
5.3 OEM Process: Material Requirements Planning
Use
This business process step is used to re-execute material requirements planning at the customer
side.
Procedure
1. Access the activity using one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Production  MRP  Planning  Multilevel SingleItem Planning
Transaction code
MD02
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Production Planner
(SAP_NBPR_PRODPLANNER-S)
Business role menu
Production  MRP  Planning  MRP - Single-Item, Multi-Level
2. On the Single-Item, Multi-Level screen, maintain in accordance with the following table:
Field name
Description
©2011 Sparta Consulting
User action and values
Page 30 of 31
Comment
AutoEdge
Scheduling Agreement With Summarize JIT Call (127): BPD
A-67-2000_OEM
Material
MRP area
1000
Plant
Scope of
planning
Product group
MRP control
parameters
Processing Keys
NETCH
Create purhase.
req.
2 (Purchase requisitions in
opening period)
Delivery
schedules
3 (Schedule lines)
Create MRP list
1 (MRP list)
Planning mode
3 (Delete and recreate
planning data)
Scheduling
1 (Basic dates will be
determined for planned
orders)
3. Confirm your entries and the following system messages. The system displays an overview of
the statistics generated and tells you that planning has been carried out.
4. Go back to the Single-Item, Multi-Level screen.
5. Choose Back (F3) to return to the SAP Easy Access screen (SAP GUI).
Or
Choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP
Home (SAP NetWeaver Business Client).
©2011 Sparta Consulting
Page 31 of 31