AutoEdge
EHP4 for SAP ERP
6.0
March 2011
English
Scheduling
Agreement
with Summarized JIT Call
(A67)
Building Block Configuration Guide
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 summarized JIT Call (A67): Configuration Guide
Contents
Scheduling Agreement with Summarized JIT Call...........................................................................3
1 Purpose........................................................................................................................................3
2 Configuration................................................................................................................................3
2.1 Configuration in the Supplier System......................................................................................3
2.1.1 Master Data Maintain.......................................................................................................3
2.1.2 Other Settings................................................................................................................12
2.2 Configuration in the OEM System.......................................................................................104
2.2.1 Master Data Maintain...................................................................................................104
2.2.2 Configuration...............................................................................................................104
©2011 Sparta Consulting
Page 2 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Scheduling Agreement with Summarized JIT Call
1 Purpose
This configuration guide provides the information you need to set up the configuration of this
building block manually.
2 Configuration
2.1 Configuration in the Supplier System
2.1.1
Master Data Maintain
2.1.1.1
Customer Master Maintenance
2.1.1.1.1 Maintaining Partner Description in Customer Master
Data
Use
The purpose of this activity is to maintain the partner description for the ship-to party in the
customer master data.
Procedure
1. Access the activity using one of the following navigation options:
©2011 Sparta Consulting
Page 3 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
SAP ECC menu
©2011 Sparta Consulting
Logistics → Sales and Distribution → Master Data → Business
Partner → Customer → Change → Complete
Page 4 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Transaction code
©2011 Sparta Consulting
XD02
Page 5 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
2. On the Customer Change Initial Screen, enter the following data and choose Continue.
©2011 Sparta Consulting
Page 6 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
User action and values
Customer
A-6701
Sales Organization
1000
Distribution Channel
10
©2011 Sparta Consulting
Page 7 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
User action and values
Division
10
©2011 Sparta Consulting
Page 8 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
3. Choose Sales Area Data.
4. Choose the Partner Functions tab, on the line SH ship-to party, make the following entries:
©2011 Sparta Consulting
Page 9 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
User action and values
Partner Functions
©2011 Sparta Consulting
Page 10 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
User action and values
Partner description
1000
©2011 Sparta Consulting
Page 11 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
5. Choose Save.
6. Choose Back.
Result
The partner description for the ship-to party in the customer master data has been maintained.
2.1.2
Other Settings
2.1.2.1
Creating Pricing Condition
Use
The purpose of this activity is to create condition records at supplier side.
Procedure
1. Access the activity using one of the following navigation options:
©2011 Sparta Consulting
Page 12 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
SAP ECC menu
©2011 Sparta Consulting
Logistics → Equipment and Tools Management → Master Data →
Conditions → Prices → Others → Create
Page 13 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Transaction code
©2011 Sparta Consulting
VK11
Page 14 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
2. On the Create Condition Record screen, enter Condition Type: PR00.
3. Choose Material with release status.
4. Choose Continue.
5. On the Create Price Condition (PR00) : Fast Entry screen, make the following entries:
©2011 Sparta Consulting
Page 15 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
Sales Organization
©2011 Sparta Consulting
Description
User action and values
1000
Page 16 of 215
Note
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
Distribution Channel
©2011 Sparta Consulting
Description
User action and values
Note
10
Direct Sales
Page 17 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
©2011 Sparta Consulting
Page 18 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Material
©2011 Sparta Consulting
Amount
Currency
Page 19 of 215
UOM
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
A-67-2000_SUP
©2011 Sparta Consulting
12000
JPY
Page 20 of 215
PC
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
6. Choose Save.
7. Choose Back twice and go back to SAP Easy Access screen.
Result
The condition record PR00 for material A-67-2000_SUP is created.
2.1.2.2
Determining Sold-To Party
Use
In this step, you assign a sold-to party number to the following criteria:
•
Vendor number (the number used by the customer for you, the component supplier)
•
Partner description (such as delivering plant)
•
Unloading point
Procedure
1. Access the activity using one of the following navigation options:
©2011 Sparta Consulting
Page 21 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Transaction code
©2011 Sparta Consulting
SPRO
Page 22 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
IMG menu
©2011 Sparta Consulting
Sales and Distribution → Sales → Sales Documents → Scheduling
Agreements with Delivery Schedules → Control EDI Inbound
Processing → Execute Sold-to Party Assignment for Release Orders
Page 23 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
2. Choose New Entries, make the following entries:
©2011 Sparta Consulting
Page 24 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Vendor
Partner desc
A-V6701
1000
©2011 Sparta Consulting
Unloading Point
Sold-to party
A-6701
Page 25 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
3. Choose Save.
Result
A sold-to party number is assigned according to the following criteria:
-
Vendor number (the number used by the customer for you, the component
supplier): A-V6701
-
Partner description (such as delivering plant): 1000
2.1.2.3
Defining Special Features for Delivery Schedules
Use
In this step, you define how the system processes delivery schedules received by Electronic Data
Interchange from a particular customer, or combination of customer/unloading point.
You must create a record for every customer! The system checks this record in Customizing for
every incoming delivery schedule. If it cannot find a record for the particular sold-to party, it issues
an error message and stops the processing of the IDoc.
Procedure
1. Access the activity using one of the following navigation options:
©2011 Sparta Consulting
Page 26 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Transaction code
©2011 Sparta Consulting
SPRO
Page 27 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
IMG menu
©2011 Sparta Consulting
Sales and Distribution → Sales → Sales Documents →Scheduling
Agreements with Delivery Schedules → Control EDI Inbound
Processing → Define Special Features for Scheduling Agreement
Page 28 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
2. Choose New Entries, make the following entries:
©2011 Sparta Consulting
Page 29 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Sold-To Party
Unloading Point
A-6701
©2011 Sparta Consulting
Check PO number
X
Page 30 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
3. Choose Save.
Result
How the system processes delivery schedules received by Electronic Data Interchange from
customer A-6701, or combination of customer/unloading point is defined.
A record for every customer is needed! The system checks this record in Customizing for every
incoming delivery schedule. If it cannot find a record for the particular sold-to party, it issues an
error message and stops processing of the IDoc.
2.1.2.4
Defining Call Control
Procedure
1. Access the activity using one of the following navigation options:
©2011 Sparta Consulting
Page 31 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Transaction code
©2011 Sparta Consulting
SPRO
Page 32 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
IMG menu
©2011 Sparta Consulting
Logistics Execution → JIT Inbound → Call Control → Define
Call Control
Page 33 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
2. Choose New Entries.
3. On the New Entries: Overview of Added Entries screen, enter the following values:
©2011 Sparta Consulting
Page 34 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
Description
User action and values
Control
YA01
Call Ctrl Short Text
General control MAB
©2011 Sparta Consulting
Page 35 of 215
Note
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
Logging Active
©2011 Sparta Consulting
Description
User action and values
Deselect
Page 36 of 215
Note
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
4. Choose Save.
5. Choose Back.
6. In the Call Control sub dialog, choose Control YA01, and then choose Status change → actions
from Dialog Structure.
7. On the New Entries: Overview of Added Entries screen, enter the following values:
©2011 Sparta Consulting
Page 37 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
CurrStatus
©2011 Sparta Consulting
New Status
Action
VF
CREA
Page 38 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
CurrStatus
New Status
Action
VF
VF
MODI
©2011 Sparta Consulting
Page 39 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
8. Choose Save.
9. Choose Processing statuses and actions from Dialog Structure.
©2011 Sparta Consulting
Page 40 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
PrSt.Curr
Action
Prc.st.new
CREA
0000
0000
JIT2
1000
0000
MODI
1000
0000
VL10
7000
1000
JIT2
1000
1000
MODI
1000
1000
VL10
7000
7000
MODI
7000
©2011 Sparta Consulting
Page 41 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
PrSt.Curr
Action
7000
REOR
©2011 Sparta Consulting
Prc.st.new
Page 42 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
10. Choose Save.
11. Choose Back and go to the IMG menu.
Result
The call control type YA01 is defined for the JIT call processing, which is used to control actions
based on processing status. With this flexible action net you can also realize various processes in a
call control. You can, for example, control a repeat order or a cancellation differently to a standard
JIT call.
2.1.2.5
Defining Control Profile for Summarized JIT Calls
Procedure
1. Access the activity using one of the following navigation options:
©2011 Sparta Consulting
Page 43 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Transaction code
©2011 Sparta Consulting
SPRO
Page 44 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
IMG menu
©2011 Sparta Consulting
Logistics Execution → JIT Inbound → Define Control Profiles →
Define Control Profile for Summarized JIT Calls (SumJC)
Page 45 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
2. Choose New Entries.
3. On the New Entries: Details of Added Entries screen, make the following entries:
©2011 Sparta Consulting
Page 46 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
Description
User action and values
SumJC Profile
YA0000000001
Profile Text
MAB_HEADERDATAF:DELIVERYSPLIT/IDOC
Quantity Change
Change in Quantity not permitted
Procg Status Split
Warning, yellow
24:00
Alarm level,red
10:00
Call Relevance
Calls are always relevant
SumJC DG Split
No additional JIT criteria, standard splitting
SumJC ID Level
Call header (=external call number)
Ref. No.Check
Deselected
©2011 Sparta Consulting
Page 47 of 215
Note
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
ATP Check
©2011 Sparta Consulting
Description
User action and values
No ATP Check
Page 48 of 215
Note
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
4. Choose Save.
5. Choose New Entries.
6. On the New Entries: Details of Added Entries screen, make the following entries:
©2011 Sparta Consulting
Page 49 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
Description
User action and values
SumJC Profile
YA0000000002
Profile Text
MAB-GRP-INFO FOR DELIVERYSPLIT/IDOC
Quantity Change
Change in Quantity not permitted
Procg Status Split
Warning, yellow
24:00
Alarm level,red
10:00
Call Relevance
Only Relevant for CGs without production
scheduling
SumJC DG Split
Split per grouping information
SumJC ID Level
Components group/discrete material (=grouping
information)
Ref. No.Check
Deselected
©2011 Sparta Consulting
Page 50 of 215
Note
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
ATP Check
©2011 Sparta Consulting
Description
User action and values
No ATP Check
Page 51 of 215
Note
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
7. Choose Save.
8. Choose Back and go to the IMG menu.
Result
Control profile for summarized JIT calls YA0000000001 and YA0000000002 are maintained.
2.1.2.6
Defining Components Group Determination
Procedure
1. Access the activity using one of the following navigation options:
©2011 Sparta Consulting
Page 52 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Transaction code
©2011 Sparta Consulting
SPRO
Page 53 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
IMG menu
©2011 Sparta Consulting
Logistics Execution → JIT Inbound → Define Control Profiles
→ Define Components Group Determination
Page 54 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
2. Choose New Entries.
3. On the New Entries: Details of Added Entries screen, enter the following values:
©2011 Sparta Consulting
Page 55 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
Description
values
Determ.Profile
YA000001
Text determn prof.
MAB CALL CMP AS PART GROUP
MATERIAL
Prio.unload.point
Not relevant for determination – copy to JIT call
Prio. of assby locn
Obligatory for determining components groups
Comp.groups mat.
Not relevant for determining components
groups
Prio.of prod.vers.
Not relevant for determining components
groups
©2011 Sparta Consulting
Page 56 of 215
Note
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
Derivation of CG
mat
©2011 Sparta Consulting
Description
values
Component groups material (EDI customer
exit/dialog)
Page 57 of 215
Note
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
4. Choose Save.
5. Choose Back and go to the IMG menu.
Result
Component group determination YA000001 is maintained.
2.1.2.7
Defining Control Profile for Delivery
Procedure
1. Access the activity using one of the following navigation options:
©2011 Sparta Consulting
Page 58 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Transaction code
©2011 Sparta Consulting
SPRO
Page 59 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
IMG menu
©2011 Sparta Consulting
Logistics Execution → JIT Inbound → Define Control Profiles
→ Define Control Profile for Delivery
Page 60 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
2. Choose New Entries.
3. On the New Entries: Details of Added Entries screen, make the following entries:
©2011 Sparta Consulting
Page 61 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
Description
User action and values
Profile dely creatn
YA000001
Text ctrl profile
PAB_LF01 / PRODN IN IDOC
Not rel. picking
Selected
HU creation
Handling units not created
PackTransProfile
0002
Type Log.Match
No logistics matching
Select open dely
No goods issue posted
Type of Ref. No.
External call number
Ref. No. in Delivery
Header and item lever (Segment E1EDL51
and 52)
Ref. No. in BillDoc.
No reference numbers in Billing Document
IDoc
©2011 Sparta Consulting
Page 62 of 215
Note
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
Status Update on GI
©2011 Sparta Consulting
Description
User action and values
Deselected
Page 63 of 215
Note
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
4. Choose Save.
5. Choose Back and go to the IMG menu.
Result
Control profile for delivery YA000001 is maintained.
2.1.2.8
Creating JIT Customer
Use
This step is to create JIT customer at the supplier side.
Procedure
1. Access the activity using one of the following navigation options:
©2011 Sparta Consulting
Page 64 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
SAP ECC menu
©2011 Sparta Consulting
Logistics → Logistics Execution → JIT Inbound → Basic
Data → Maintain Customer
Page 65 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Transaction code
©2011 Sparta Consulting
JITV
Page 66 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
2. On the Change View Maintain JIT Customer: Overview screen, choose Maintain JIT Customer
in the Dialog Structure and then choose New Entries.
3. On the New Entries: Details of Added Entries screen, make the following entries:
©2011 Sparta Consulting
Page 67 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
Description
User action and values
JIT Customer
UCAR
Sold-to party
A-6701
Partner Descr
1000
Cust. time zone
JAPAN
Usage
S
Determ.Profile
YA000001
Sig.monitor active
Select
CallType
Summarized JIT Call [D]
MaintenanceMode
Discrete Material /SumJC
SumJC Profile
YA0000000001
©2011 Sparta Consulting
Page 68 of 215
Note
(or your personalized
data)
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
Profile dely creatn
©2011 Sparta Consulting
Description
User action and values
YA000001
Page 69 of 215
Note
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
4. Choose Save.
5. Choose Back.
6. In the Maintain JIT Customer sub dialog box, on the Change View Maintain JIT Customer:
Overview screen, choose JIT customer: UCAR.
7. Choose Conversion of external status information from Dialog Structure.
8. Choose New Entries.
9. On the New Entries: Overview of Added Entries screen, make the following entries:
©2011 Sparta Consulting
Page 70 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Stat. Info
Ext. Status
VF
0000
VF
1200
VF
©2011 Sparta Consulting
Page 71 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Stat. Info
Ext. Status
1400
VF
©2011 Sparta Consulting
Page 72 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
10. Choose Maintain Lead Times from Dialog Structure:
©2011 Sparta Consulting
Page 73 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
Description
User action and values
CG Type
Basis Time
Time of External Status Change
Ext. Status
VF
Days
TimeShift
©2011 Sparta Consulting
02:00:00
Page 74 of 215
Note
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
Description
User action and values
Prelim.Run
©2011 Sparta Consulting
Page 75 of 215
Note
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
11. Choose Save.
12. Choose Maintain Destinations from Dialog Structure.
13. Choose New Entries.
14. Make the following entries :
©2011 Sparta Consulting
Page 76 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
Description
User action and values
Destination
WSP3
JIT Customer
UCAR
Unloading Point
Tor 10
Assy Loc.
YA0004
DestText 1
©2011 Sparta Consulting
Page 77 of 215
Note
Supply area
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
Description
User action and values
DestText 2
©2011 Sparta Consulting
Page 78 of 215
Note
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
15. Choose Save.
16. Choose Back.
17. In the Maintain Destination sub dialog box, on the Change View Maintain Destination:
Overview screen, choose WSP3.
18. Choose Maintain Components Group Types from Dialog Structure.
19. On the Change View Maintain Components Group Types: Details screen, make the following
entries:
©2011 Sparta Consulting
Page 79 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
Description
User action and values
Comp.Grp Type
WSP3
Destination
WSP3
CG Material
A-67-2000_SUP
Call Control
YA01
Plant
1000
©2011 Sparta Consulting
Page 80 of 215
Note
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
Description
CGText 1
©2011 Sparta Consulting
User action and values
Component Group A67
Page 81 of 215
Note
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
20. Choose Save.
21. Choose Back and go back the SAP Easy Access screen.
Result
•
JIT customer UCAR is created.
•
The external status information is maintained.
•
The lead time for the JIT customer UCAR is defined.
•
The inbound destination WSP3 is defined for the JIT customer UCAR.
•
The component group type WSP3 is defined for the JIT customer UCAR.
2.1.2.9
Assigning Sales Order Types Permitted for Sales
Areas
Use
In this menu option, you allocate the allowed order types to each sales area.
Procedure
1. Access the activity using one of the following navigation options:
©2011 Sparta Consulting
Page 82 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Transaction code
©2011 Sparta Consulting
SM30 (Customizing Object V_TVAKZ)
Page 83 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
IMG menu
©2011 Sparta Consulting
Sales and Distribution → Sales → Sales Documents → Sales Documents
Header → Assign Sales Area To Sales Document Types
Page 84 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
2. In the Choose Activity dialog box, double-click Assign sales order types permitted for sales
areas.
3. On the Change View Sales Documents. Allowed Order Types per Sales Org.: Overview screen,
choose New Entries and make the following entries:
©2011 Sparta Consulting
Page 85 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Ref.S
RefD
Div
SaTy
1000
10
10
LZJ
©2011 Sparta Consulting
Page 86 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
4. Choose Save and then choose Back.
2.1.2.10
Creating Scheduling Agreement LZJ
Use
The purpose of this activity is to create Sales Scheduling Agreement.
Prerequisites
•
Related customizing must exist.
•
Related master data is ready.
Perform the following check for your customer master data, A-6701 and so on.
Transaction code: XD02 (Changing Customer master data)
Menu path: Sales Area → Partner
Check whether the partner description 1000 exists for partner function SH, which is
important for Scheduling agreement, release processing. The incoming customer
scheduling agreement (56xxxxxxxx and so on) will use this entry as well as PO No.,
Customer-material, and sold-to party, to search the corresponding SD scheduling
agreement, 35xxxxxx and so on.
If not, add the partner description manually.
Procedure
1. Access the activity using one of the following navigation options:
©2011 Sparta Consulting
Page 87 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
SAP ECC menu
©2011 Sparta Consulting
Logistics → Logistics Execution → JIT Inbound → Environment →
Master Data → Scheduling Agreement (SD) → Create
Page 88 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Transaction code
©2011 Sparta Consulting
VA31
Page 89 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
2. On the Create Scheduling Agreement: Initial Screen, make the following entries:
©2011 Sparta Consulting
Page 90 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
Description
User action and values
Sched.Agreemt Type
LZJ
Sales Organization
1000
Distribution Channel
10
Division
10
Sales Office
1000
©2011 Sparta Consulting
Page 91 of 215
Note
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
Sales Group
©2011 Sparta Consulting
Description
User action and values
100
Page 92 of 215
Note
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
3. Confirm your entries.
4. On the Create JIT Scheduling Agt: Overview screen, enter the following values:
©2011 Sparta Consulting
Page 93 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
Description
User action and values
JIT Scheduling.Agt.
35006701
Sold-to party
A-6701
Ship-to Party
A-6701
©2011 Sparta Consulting
Page 94 of 215
Note
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
PO Number
©2011 Sparta Consulting
Description
User action and values
5600006701
Page 95 of 215
Note
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
5. On the Item Overview tab, enter the following entries:
©2011 Sparta Consulting
Page 96 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
Description
User action and values
Item
10
Material
A-67-2000_SUP
Rounding Qty
0
Customer Material
Number
A-67-2000_OEM
PO Item
10
©2011 Sparta Consulting
Page 97 of 215
Note
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
Storage location
©2011 Sparta Consulting
Description
User action and values
1040
Page 98 of 215
Note
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
6. Choose Save.
7. Choose Back and go back to SAP Easy Access screen.
Result
The Sales Scheduling Agreement 35006701 with scheduling agreement type LZJ is created.
2.1.2.11
Creating Copy Control for Delivery
Use
This activity copy controls.
Procedure
1. Access the activity using one of the following navigation options:
©2011 Sparta Consulting
Page 99 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Transaction code
©2011 Sparta Consulting
VTLA
Page 100 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
IMG menu
©2011 Sparta Consulting
Logistics Execution → Shipping → Copying Control → Specify
Copy Control for Deliveries
Page 101 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
2. On the Display View Header: Overview screen, choose Display  Change.
3. Select the required combinations of source sales document type and delivery type. Doubleclick Item in the Dialog Structure pane.
4. Choose New Entries.
5. Make the following entries:
©2011 Sparta Consulting
Page 102 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Sales
Doc
Type
Delivery
Type
ItemCat
Order
requirements
Item
Data
Item
Ext.
System
Business
Data
Update
doc
flow
LZJ
LF
LZN
101
101
0
2
X
©2011 Sparta Consulting
Page 103 of 215
+/-
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
6. Choose Save.
7. Choose Back.
Result
Controls are copied.
2.2 Configuration in the OEM System
2.2.1
Master Data Maintain
2.2.2
Configuration
2.2.2.1
Creating Message Record for Forecast Delivery
Schedule in MM Scheduling Agreement
Use
The purpose of this activity is to creating the message record for forecast delivery schedule in MM
Scheduling Agreement.
Procedure
1. Access the activity using one of the following navigation options:
©2011 Sparta Consulting
Page 104 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
SAP ECC menu
©2011 Sparta Consulting
Logistics → Materials Management → Purchasing → Master Data →
Messages → Scheduling Agreement Delivery Schedule → Create
Page 105 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Transaction code
©2011 Sparta Consulting
MN10
Page 106 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
2. On the Create Output – Condition Records: Purch.SchAgrRelease screen, make the following
entries:
©2011 Sparta Consulting
Page 107 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
Output type
©2011 Sparta Consulting
Description
User action and values
YAH1
Page 108 of 215
Note
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
3. Choose Key Combination.
4. Confirm the dialog box.
5. Make the following entries:
©2011 Sparta Consulting
Page 109 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
Description
User action and values
Purch Organization
1000
Vendor
A-V6701
Funct
VN
Medium
6
©2011 Sparta Consulting
Page 110 of 215
Note
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
Date/Time
©2011 Sparta Consulting
Description
User action and values
3
Page 111 of 215
Note
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
6. Choose Save.
7. Choose Back and go to SAP Easy Access screen.
2.2.2.2
Partner Profile, Only Basic Data
Use
Partner profiles for EDI communication are created at the OEM side.
Procedure
1. Access the activity using one of the following navigation options:
©2011 Sparta Consulting
Page 112 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
SAP ECC menu
©2011 Sparta Consulting
Logistics → Logistics Execution → Internal Whse Processes →
Communication with External Systems → ALE Administration →
Runtime Settings → Partner Profiles
Page 113 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Transaction code
©2011 Sparta Consulting
WE20
Page 114 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
2. On the right area of the Partner profiles screen, select Partner profiles → Partner type LI.
3. Choose Create.
4. On the right top area of Partner profiles screen, make the following entries:
©2011 Sparta Consulting
Page 115 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
Description
Partner No.
User action and
values
Note
A-V6701
The system assigns this number if you
create a master record in an application
(for example, purchasing, sales). The EDI
partner is identified uniquely via the
partner number and partner type.
If you define your own partner types, they
are also identified by this number.
©2011 Sparta Consulting
Page 116 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
5. On the right area of Partner profiles screen, select Post processing: permitted agent.
6. Make the following entries:
©2011 Sparta Consulting
Page 117 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
Description
User action
and values
Note
Ty.
Agent type
US
Agent type
Classifies the recipient of error notifications.
Examples
'US': An individual agent is notified.
'O': Agent type is an organizational unit: all
persons assigned to this organizational unit
are notified.
Dependencies
Individual persons are assigned to the
positions, organizational units and so on in
the PD Organizational Model (PD-ORG).
Agent
AM-MUSTER
Permitted users: ID
Specifies the job (person or group of people)
to be notified if processing errors occur on
the IDoc interface. You can define up to
three different jobs:
In the inbound or outbound partner profiles
for special partners, messages and direction.
In the general partner profiles for special
partners.
In the general IDoc Administration settings.
Use
If an error occurs, only one (the most
specific) job is notified. If an error occurs in
the ORDERS message for partner HUGH,
the system first attempts to determine
whether a job responsible for ORDERS and
HUGH is defined. If this is not the case, the
job defined for HUGH (required entry) is
notified.
The IDoc administrator is notified if HUGH
does not exist at all in the partner profiles.
Examples
If the recipient type is 'US' ('user'), enter the
name of the SAP user who is to be notified.
If the recipient type is 'O' ('organizational
unit'), enter the organizational unit whose
personnel are to be notified.
Dependencies
This specification depends on how you have
configured the PD Organizational Model (PDORG).
©2011 Sparta Consulting
Page 118 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
Description
User action
and values
Note
Lang.
Language of
notification
EN
If an error occurs, SAPoffice notifies the
permitted user in this language.
©2011 Sparta Consulting
Page 119 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
7. Choose Save.
If the partner already exists, you can change the partner or choose a different
customer.
If the customer number does not exist in your system, the following error message
appears: Enter a permitted partner number.
Result
Partner profile for A-V6701 is created successfully.
2.2.2.3
Partner Profile Outbox for DELFOR and SEQJIT
Use
Outbound parameters in partner profiles are created at OEM side.
Procedure
1. Access the activity using one of the following navigation options:
©2011 Sparta Consulting
Page 120 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
SAP ECC menu
©2011 Sparta Consulting
Logistics → Logistics Execution → Internal Whse Processes →
Communication with External Systems → ALE Administration →
Runtime Settings → Partner Profiles
Page 121 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Transaction code
©2011 Sparta Consulting
WE20
Page 122 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
2. On the right area of the Partner profiles screen, select Partner profiles → Partner type LI → AV6701.
3. On the right area of Partner profiles screen, choose Insert under Outbound parmtrs.
4. On the Partner profiles: Outbound parameters screen, make the following entries:
©2011 Sparta Consulting
Page 123 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
Description
User action
and values
Note
Partner Role
Partner
function of
sender
VN
As an optional parameter, the partner
function containing the sender and the
recipient can be specified. Example: 'VN' for
'vendor' or 'AG' for 'sold-to party'.
SNDPFC, SNDPRN and SNDPRT provide a
unique ID for the sender. They are among
the key fields in the partner profiles, which
are used in inbound processing, for example,
to determine the process code and therefore
the internal processing for the IDoc.
Therefore, if the sender function has been
specified in the inbound partner profiles, the
external system must maintain the field with
the corresponding value.
©2011 Sparta Consulting
Page 124 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
Description
Message type
User action
and values
Note
DELFOR
In EDI, message types are assigned to SAP
document types uniquely. Their names
correspond as much as possible to those of
the UN/EDIFACT standard. ALE scenarios,
on the other hand, have no EDIFACT
correspondence, for example when master
data is transmitted.
Example
©2011 Sparta Consulting

ORDERS for purchase order data

INVOIC for invoice data
Page 125 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
5. On the bottom area of the screen Partner profiles: Outbound parameters, select outbound
options tab.
6. Make the following entries:
©2011 Sparta Consulting
Page 126 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
Description
User action
and values
Note
Receiver Port
Z_AUTO
Specifies how the IDocs are transferred to
the EDI subsystem. There are various
technical possibilities for this communication
known as port types. The choice of port type
also depends on the technical capabilities of
the EDI subsystem.
Output Mode
Transfer IDoc
immed.
Output is started immediately for each
individual IDoc.
Basic type
DELFOR02
Basic types can be used without additional
coding for data communication: SAP supplies
functions modules, which enter application
data in the basic types. Basic types can be
extended by the customer with upwardcompatibility.
©2011 Sparta Consulting
Page 127 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
Description
Cancel
Processing
After Syntax
Error
©2011 Sparta Consulting
User action
and values
Note
X
If you select the syntax check, the IDoc
Interface terminates the processing if a
syntax error is found.
If you do not select the syntax check, the
IDoc Interface continues the processing. You
receive a message that a syntax error was
found.
Page 128 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
7. Choose Save.
8. Repeat steps 1-7 to make the following entries:
©2011 Sparta Consulting
Page 129 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Partn
er No.
Partn.
Type
Partner
Role
AV6701
LI
VN
©2011 Sparta Consulting
Mess
age
Type
Receiv
er Port
Packet
Size
IDoc
Type
SEQJ
IT
Z_AUT
O
1
SEQJ
IT03
Page 130 of 215
Transfe
r IDoc
Immed.
Cancel
Processing
After Syntax
Error
X
X
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Result
The message types DELFOR and SEQJIT are maintained for partner profile A-V6701.
2.2.2.4
Partner Profiles Message Control for DELFOR and
SEQJIT
Use
Message Control of outbound parameters in partner profiles is created at OEM side.
Procedure
1. Access the activity using one of the following navigation options:
©2011 Sparta Consulting
Page 131 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
SAP ECC menu
©2011 Sparta Consulting
Logistics → Logistics Execution → Internal Whse Processes →
Communication with External Systems → ALE Administration →
Runtime Settings → Partner Profiles
Page 132 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Transaction code
©2011 Sparta Consulting
WE20
Page 133 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
2. On the right area of the Partner profiles screen, select Partner profiles → Partner type LI → AV6701.
3. On the right area of Partner profiles: Outbound parmtrs screen, double-click following item.
©2011 Sparta Consulting
Page 134 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
Description
Partner Role
©2011 Sparta Consulting
User action and values
VN
Page 135 of 215
Note
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
Description
Message Type
©2011 Sparta Consulting
User action and values
DELFOR
Page 136 of 215
Note
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
4. On the bottom area of the Partner profiles: Outbound parameters screen, select Message
Control options tab.
5. Make the following entries:
©2011 Sparta Consulting
Page 137 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
Description
Application
User action
and values
Note
EL
This key field is assigned to the
corresponding message control (output
control) field. Together with the output type, it
uniquely identifies a message type in
message control that can then be assigned
uniquely to an IDoc type.
Examples
'EA' = 'Purchasing RFQ' in Materials
Management (MM).
'V3' = 'Billing' in Sales and Distribution (SD).
Message type
YAH1
This key field is assigned to the
corresponding message control (output
control) field. Together with the application, it
uniquely identifies a message type in
message control that can then be assigned
uniquely to an IDoc type.
Examples
'NEW' = 'New message', such as a new
purchase order (application 'EF') or a new
request for quotation (application 'EA').
'LAVA' = 'Shipping notification' in dispatch
(application 'V2').
©2011 Sparta Consulting
Page 138 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
Description
Process code
User action
and values
Note
ME14
The IDoc Interface uses the process code
to determine the application selection
module, which converts the SAP document
into an IDoc.
Examples
ME10: Purchase order (MM)
SD09: Invoice
©2011 Sparta Consulting
Page 139 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
6. Choose Save.
7. Repeat steps 1-6 to make the following entries:
©2011 Sparta Consulting
Page 140 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Partner
No
Partn.Type
Partner
Role
Message
Type
Application
Message
Type
Process
Code
A-V6701
LI
VN
SEQJIT
PA
OJIT
SJCL
©2011 Sparta Consulting
Page 141 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Result
The message type YAH1 has been maintained for message type DELFOR and the message type
OJIT has been maintained for message type SEQJIT.
2.2.2.5
Defining JIT Call Control
Procedure
Step 1: Define Processing Status
1. Access the activity using one of the following navigation options:
©2011 Sparta Consulting
Page 142 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Transaction code
©2011 Sparta Consulting
SPRO
Page 143 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
IMG menu
©2011 Sparta Consulting
Logistics Execution → JIT Inbound → Call Control → Define
External Status and Internal Processing Status
Page 144 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
2. On the Change View Define Internal Processing Status: Overview screen, choose the Define
Internal Processing Status from Dialog Structure.
3. Ensure the following values exist in the table. Otherwise, on the New Entries: Overview of
Added Entries screen, choose New Entries to enter the correspondent values:
©2011 Sparta Consulting
Page 145 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
ProcStat
Text
Call not saved/deleted
0000
JIT-call created
JIT 指示生成済
1000
JIT-call modified
JIT 指示変更済
1400
JITOUT MAB: ASN created
JIT 出力 MSB：ASN 生成済
1600
JITOUT MAB: GR posted
JIT 出力 MSB：入庫転記済
1700
JITOUT MAB: JC finished
JIT 出力 MSB：JC 完了
©2011 Sparta Consulting
Page 146 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
ProcStat
Text
7000
Delivery created
出荷生成済
©2011 Sparta Consulting
Page 147 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
4. Choose Save.
5. Choose Back and go to the IMG menu.
Step 2: Define JIT Call control
1. Access the activity using one of the following navigation options:
©2011 Sparta Consulting
Page 148 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Transaction code
©2011 Sparta Consulting
SPRO
Page 149 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
IMG menu
©2011 Sparta Consulting
Logistics Execution → JIT Outbound → Call Control → Define
Call Control
Page 150 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
2. Choose New Entries.
3. On the New Entries: Overview of Added Entries screen, make the following entries:
©2011 Sparta Consulting
Page 151 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
Description
User action and values
Control
YA01
Call Ctrl Short Text
Summarized JIT call control
©2011 Sparta Consulting
Page 152 of 215
Note
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
Logging Active
©2011 Sparta Consulting
Description
User action and values
Deselect
Page 153 of 215
Note
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
4. Choose Save.
5. Choose Back.
6. In the Call Control sub dialog, choose Control YA01, and then choose Processing statuses and
actions from Dialog Structure.
©2011 Sparta Consulting
Page 154 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
PrSt.Curr
Action
Prc.st.new
OCRE
0000
0000
OMOD
0000
0000
OSDD
1400
0000
OSHP
1400
1400
OGRE
1600
1600
OFIN
1700
1700
OARC
©2011 Sparta Consulting
Page 155 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
PrSt.Curr
Action
1700
OREO
©2011 Sparta Consulting
Prc.st.new
Page 156 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
7. Choose Save.
8. Choose Back and go to the IMG menu.
Result
The call control YA01 is maintained.
2.2.2.6
Creating JIT Call Profile
Use
In this step, JIT call profile is defined, which is assigned to a control cycle, thereby setting the
automatic controls for all JIT calls created via this control cycle.
A JIT call profile consists of:
•
The JIT call type (the summarized JIT call is currently available)
•
The partner role
•
The type of summary
•
The time definition
Procedure
1. Access the activity using one of the following navigation options:
©2011 Sparta Consulting
Page 157 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Transaction code
©2011 Sparta Consulting
SPRO
Page 158 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
IMG menu
©2011 Sparta Consulting
Logistic Execution → JIT Outbound → Control Profiles → Define
JIT Call Profile
Page 159 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
2. Choose New Entries
3. On the New Entries: Details of Added Entries screen, make the following entries:
©2011 Sparta Consulting
Page 160 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
Description
User action and values
JC profile
YA01
JIT call profil
SumJC (Outbound)
SumJC ( 送信)
JIT Call type
S
Partner Role JC
VN
Summary
Summary by plant, unloading point
Time definition
Call Control
©2011 Sparta Consulting
YA01
Page 161 of 215
Note
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
Messg Det. Usage
©2011 Sparta Consulting
Description
User action and values
Message Determination Required
Page 162 of 215
Note
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
4. Choose Save (Ctrl + S).
5. Choose Back (F3).
Result
The summarized JIT call profile ZJC1 has been created.
2.2.2.7
Creating Condition: JIT Call
Use
The purpose of this activity is to create the message condition for JIT calls.
Procedure
1. Access the activity using one of the following navigation options:
©2011 Sparta Consulting
Page 163 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
SAP ECC menu
©2011 Sparta Consulting
Logistics → Production → KANBAN → JIT Call → Message
Conditions → Create
Page 164 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Transaction code
©2011 Sparta Consulting
PJNK1
Page 165 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
2. On the Create Output - Condition Record: JIT Call screen, make the following entries:
©2011 Sparta Consulting
Page 166 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
Output Type
©2011 Sparta Consulting
Description
User action and values
OJIT
Page 167 of 215
Note
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
3. Choose Key Combination (Enter).
4. On the key Combination screen, select following checkbox:
©2011 Sparta Consulting
Page 168 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
Description
User action and values
Plant/JC Profile/vendor
©2011 Sparta Consulting
Page 169 of 215
Note
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
5. Choose Enter.
6. On the Create Condition Records (Outbound JIT-Call):Fast Entry screen, select the following
entry:
©2011 Sparta Consulting
Page 170 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
Description
User action and values
Plant
1000
JC Profile
YA01
Vendor
A-V6701
Funct
Medium
©2011 Sparta Consulting
Partner Function
Note
VN
6
Page 171 of 215
EDI
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
Date/Time
©2011 Sparta Consulting
Description
User action and values
3
Page 172 of 215
Note
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
7. Choose Save (Ctrl + S).
Result
The message condition for summarized JIT call OJIT for A-V6701 has been created.
2.2.2.8
Creating MM Scheduling Agreement
Use
The purpose of this activity is to create the scheduling agreement, which is to be used in the
replenishment of external procured components with KANBAN.
Procedure
1. Access the activity using one of the following navigation options:
©2011 Sparta Consulting
Page 173 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
SAP ECC menu
©2011 Sparta Consulting
Logistics → Material Management → Purchasing → Master Data →
Subsequent Settlement → Vendor Rebate Arrangement → Environment →
Vendor → Environment → Outline agreement → Create
Page 174 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Transaction code
©2011 Sparta Consulting
ME31
Page 175 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
2. On the Create Contract: Initial Screen, make the following entries:
©2011 Sparta Consulting
Page 176 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
Description
User action and values
Vendor
A-V6701
Agreement Type
LPA
Agreement
5600006701
Organizational Data
Purch. Organization
10000
Purchasing Group
100
Default Data for Items
Plant
©2011 Sparta Consulting
1000
Page 177 of 215
Note
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
Description
User action and values
Storage Location
1040
©2011 Sparta Consulting
Page 178 of 215
Note
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
3. Choose Continue (Enter).
4. On the Create Scheduling Agreement: Header Data screen, make the following entries:
©2011 Sparta Consulting
Page 179 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
Description
User action and values
Validity end
For example: 2099.12.31
Invoicing party
A-V6701
©2011 Sparta Consulting
Page 180 of 215
Note
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
Suppl. vendor
©2011 Sparta Consulting
Description
User action and values
A-V6701
Page 181 of 215
Note
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
5. On the Create Scheduling Agreement: Item Overview screen, make the following entries:
©2011 Sparta Consulting
Page 182 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
Description
User action and values
Item
10
Material
A-67-2000_OEM
Target Quantity
1000000
©2011 Sparta Consulting
Page 183 of 215
Note
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
Net Price
©2011 Sparta Consulting
Description
User action and values
120
Page 184 of 215
Note
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
6. Select the item and choose Item Details.
7. On the Display Scheduling Agreement: Item 0010 screen, make the following entries:
©2011 Sparta Consulting
Page 185 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
Tax Code
©2011 Sparta Consulting
Description
User action and values
V1
Page 186 of 215
Note
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
8. Choose Additional data and make the following entries:
©2011 Sparta Consulting
Page 187 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
Kanban Indicat.
©2011 Sparta Consulting
Description
User action and values
Z
Page 188 of 215
Note
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
Creation profile
©2011 Sparta Consulting
Description
User action and values
YA02
Page 189 of 215
Note
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
9. Choose Save.
Result
The scheduling agreement 5600006701 with type LPA has been created.
2.2.2.9
Defining Replenishment Strategies for External
Procurement
Use
The purpose of this activity is to define replenishment strategies for external procurement.
Procedure
1. Access the activity using one of the following navigation options:
©2011 Sparta Consulting
Page 190 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Transaction code
©2011 Sparta Consulting
SPRO
Page 191 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
IMG menu
©2011 Sparta Consulting
Logistic Execution → JIT Outbound → Summarized JIT Call →
Define Replenishment Strategies For External Procurement
Page 192 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
2. On the Change View “ Replenishment Strategy: Ex. Procurement for SumJC”: Over screen,
select following entry:
©2011 Sparta Consulting
Page 193 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
Description
User action and values
Plant
1000
Ext. Procurement.
YA01
©2011 Sparta Consulting
Page 194 of 215
Note
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
Replenishment
Strategy
Description
©2011 Sparta Consulting
Description
User action and values
Rep. Strategy: Ext. Proc. for Sum. JC
補充方針：サマリ JC のための外部調達
Page 195 of 215
Note
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
3. Choose Details.
4. On the Change View “ Replenishment Strategy: Ex. Procurement for SumJC “: Deta screen,
make the following entries:
©2011 Sparta Consulting
Page 196 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
Description
User action and values
Trans.Type
101
Variable Source
X
Use PIs
No functional use, packing
instruction is a commentary
Ctrl Cycle Card
CONTROLCYCLE
©2011 Sparta Consulting
Page 197 of 215
Note
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
Print Function
©2011 Sparta Consulting
Description
User action and values
PK_CONTROLCYCLE_PRINT
Page 198 of 215
Note
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
5. Choose Save (Ctrl + S).
6. Choose Back (F3).
Result
The external procurement strategy YA01 is maintained.
2.2.2.10
Manual Step: Creating Control Cycle
Use
The control cycle is required when you create summarized JIT call.
Procedure
1. Access the activity using one of the following navigation options:
©2011 Sparta Consulting
Page 199 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
SAP ECC menu
©2011 Sparta Consulting
Logistics → Production → KANBAN → Control Cycle → Control
Cycle Maintenance
Page 200 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Transaction code
©2011 Sparta Consulting
PKMC
Page 201 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
2. On the Control Cycle Maintenance: Display screen, make the following entries and choose
Data Selection (F8).
©2011 Sparta Consulting
Page 202 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
Description
Plant
©2011 Sparta Consulting
User action and values
1000
Page 203 of 215
Note
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
3. On the Control Cycle Maintenance: Display screen, choose Display ↔ Change (F7) to switch to
change mode.
4. On the Control Cycle Maintenance: Change screen, choose Create Control Cycle.
5. In the Create Control Cycle dialog box, choose Manual SumJC, and make the following entry,
then choose Continue (Enter).
©2011 Sparta Consulting
Page 204 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
Material
©2011 Sparta Consulting
Description
User action and values
A-67-2000_OEM
Page 205 of 215
Note
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
Supply Area
©2011 Sparta Consulting
Description
User action and values
YA0004
Page 206 of 215
Note
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
6. On the Control Cycle Maintenance: Change screen, make the following entries.
©2011 Sparta Consulting
Page 207 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
Description
User action and values
Call Item Qty
10
No.Load Carrier
1
©2011 Sparta Consulting
Page 208 of 215
Note
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
Ext. Procurement
©2011 Sparta Consulting
Description
User action and values
YA01
Page 209 of 215
Note
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
7. Choose Flow Control Tab page and make the following entries:
©2011 Sparta Consulting
Page 210 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
JIT call Profile
©2011 Sparta Consulting
Description
User action and values
YA01
Page 211 of 215
Note
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
8. Choose Enter.
9. Choose External Procurement tab page and make the following entries:
©2011 Sparta Consulting
Page 212 of 215
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
Agreement
©2011 Sparta Consulting
Description
User action and values
5600006701
Page 213 of 215
Note
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
Field name
©2011 Sparta Consulting
Description
User action and values
Item
10
Page 214 of 215
Note
AutoEdge Scheduling Agreement with summarized JIT Call (A67): Configuration Guide
10. Choose Enter and Save.
2.2.2.11
Maintaining Source List
Use
The purpose of this activity is to create source list.
Prerequisites

Related customizing must exist.

Related master data exist.
Procedure
1. Access the activity using one of the following navigation options:
SAP ECC menu
Logistic → Logistics Execution → JIT Outbound → Environment → Master
Data → Maintain Source List
Transaction code
ME01
2. On the Maintain Source List: Initial Screen, make the following entries:
Field name
Description
User action and values
Material
A-67-2000_OEM
Plant
1000
Note
3. Choose Enter.
4. On the Maintain Source List: Overview screen, make the following entries:
Field name
Description
User action and values
Valid from
Today
Valid to
For example: 2099.12.31
Vendor
A-V6701
Porg
1000
Agmt
5600006701
Item
10
Fix
X
MRP
2
5. Choose Save.
6. Choose Back.
Result
Purchase Source List for material A-67-2000_OEM is created.
©2011 Sparta Consulting
Page 215 of 215
Note