B A67 Scen ConfigGuide Scheduling Agreement With Summarized JIT Call

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
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 2.1.1.1 Master Data Maintain 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:
Page 3 of 215
SAP ECC menu
Logistics Sales and Distribution Master Data Business Partner Customer Change Complete
Page 4 of 215
Transaction code
XD02
Page 5 of 215
2. On the Customer Change Initial Screen, enter the following data and choose Continue.
Page 6 of 215
Field name Customer Sales Organization Distribution Channel
User action and values A-6701 1000 10
Page 7 of 215
Field name Division
User action and values 10
Page 8 of 215
3. Choose Sales Area Data. 4. Choose the Partner Functions tab, on the line SH ship-to party, make the following entries:
Page 9 of 215
Field name Partner Functions
User action and values
Page 10 of 215
Field name Partner description
Page 11 of 215
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 2.1.2.1 Use
Other Settings Creating Pricing Condition
The purpose of this activity is to create condition records at supplier side.
Procedure
Page 12 of 215
SAP ECC menu
Logistics Equipment and Tools Management Master Data Conditions Prices Others Create
Page 13 of 215
Transaction code
VK11
Page 14 of 215
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:
Page 15 of 215
Field name Sales Organization
Description
Note
Page 16 of 215
Field name Distribution Channel
Description
Note Direct Sales
Page 17 of 215
Page 18 of 215
Material
Amount
Currency
UOM
Page 19 of 215
A-67-2000_SUP
12000
JPY
PC
Page 20 of 215
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 Use
Determining Sold-To Party
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
Page 21 of 215
Transaction code
SPRO
Page 22 of 215
IMG menu
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
2. Choose New Entries, make the following entries:
Page 24 of 215
Vendor A-V6701
Partner desc 1000
Unloading Point
Sold-to party A-6701
Page 25 of 215
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 Use
Defining Special Features for Delivery Schedules
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
Page 26 of 215
Transaction code
SPRO
Page 27 of 215
IMG menu
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
2. Choose New Entries, make the following entries:
Page 29 of 215
Sold-To Party A-6701
Unloading Point
Check PO number X
Page 30 of 215
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 Procedure
Defining Call Control
Page 31 of 215
Transaction code
SPRO
Page 32 of 215
IMG menu
Logistics Execution JIT Inbound Call Control Define Call Control
Page 33 of 215
2. Choose New Entries. 3. On the New Entries: Overview of Added Entries screen, enter the following values:
Page 34 of 215
Field name Control Call Ctrl Short Text
Description
User action and values YA01 General control MAB
Note
Page 35 of 215
Field name Logging Active
Description
User action and values Deselect
Note
Page 36 of 215
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:
Page 37 of 215
CurrStatus
New Status VF
Action CREA
Page 38 of 215
CurrStatus VF
New Status VF
Action MODI
Page 39 of 215
8. Choose Save. 9. Choose Processing statuses and actions from Dialog Structure.
Page 40 of 215
PrSt.Curr 0000 0000 0000 1000 1000 1000 7000
Action CREA JIT2 MODI VL10 JIT2 MODI VL10 MODI
Prc.st.new 0000 1000 1000 7000 1000 1000 7000 7000
Page 41 of 215
PrSt.Curr 7000
Action REOR
Prc.st.new
Page 42 of 215
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 Procedure
Defining Control Profile for Summarized JIT Calls
Page 43 of 215
Transaction code
SPRO
Page 44 of 215
IMG menu
Logistics Execution JIT Inbound Define Control Profiles Define Control Profile for Summarized JIT Calls (SumJC)
Page 45 of 215
2. Choose New Entries. 3. On the New Entries: Details of Added Entries screen, make the following entries:
Page 46 of 215
Field name SumJC Profile Profile Text Quantity Change Procg Status Split Warning, yellow Alarm level,red Call Relevance SumJC DG Split SumJC ID Level Ref. No.Check
Description
User action and values YA0000000001 MAB_HEADERDATAF:DELIVERYSPLIT/IDOC Change in Quantity not permitted 24:00 10:00 Calls are always relevant No additional JIT criteria, standard splitting Call header (=external call number) Deselected
Note
Page 47 of 215
Field name ATP Check
Description
User action and values No ATP Check
Note
Page 48 of 215
4. Choose Save. 5. Choose New Entries. 6. On the New Entries: Details of Added Entries screen, make the following entries:
Page 49 of 215
Field name SumJC Profile Profile Text Quantity Change Procg Status Split Warning, yellow Alarm level,red Call Relevance SumJC DG Split SumJC ID Level Ref. No.Check
Description
User action and values YA0000000002 MAB-GRP-INFO FOR DELIVERYSPLIT/IDOC Change in Quantity not permitted 24:00 10:00 Only Relevant for CGs without production scheduling Split per grouping information Components group/discrete material (=grouping information) Deselected
Note
Page 50 of 215
Field name ATP Check
Description
User action and values No ATP Check
Note
Page 51 of 215
Result
Control profile for summarized JIT calls YA0000000001 and YA0000000002 are maintained.
2.1.2.6 Procedure
Defining Components Group Determination
Page 52 of 215
Transaction code
SPRO
Page 53 of 215
IMG menu
Logistics Execution JIT Inbound Define Control Profiles Define Components Group Determination
Page 54 of 215
2. Choose New Entries. 3. On the New Entries: Details of Added Entries screen, enter the following values:
Page 55 of 215
Field name Determ.Profile Text determn prof. Prio.unload.point Prio. of assby locn Comp.groups mat. Prio.of prod.vers.
Description
values YA000001 MAB CALL CMP AS PART GROUP MATERIAL Not relevant for determination copy to JIT call Obligatory for determining components groups Not relevant for determining components groups Not relevant for determining components groups
Note
Page 56 of 215
Field name Derivation of CG mat
Description
values Component groups material (EDI customer exit/dialog)
Note
Page 57 of 215
Result
Component group determination YA000001 is maintained.
2.1.2.7 Procedure
Defining Control Profile for Delivery
Page 58 of 215
Transaction code
SPRO
Page 59 of 215
IMG menu
Logistics Execution JIT Inbound Define Control Profiles Define Control Profile for Delivery
Page 60 of 215
2. Choose New Entries. 3. On the New Entries: Details of Added Entries screen, make the following entries:
Page 61 of 215
Field name Profile dely creatn Text ctrl profile Not rel. picking HU creation PackTransProfile Type Log.Match Select open dely Type of Ref. No. Ref. No. in Delivery Ref. No. in BillDoc.
Description
User action and values YA000001 PAB_LF01 / PRODN IN IDOC Selected Handling units not created 0002 No logistics matching No goods issue posted External call number Header and item lever (Segment E1EDL51 and 52) No reference numbers in Billing Document IDoc
Note
Page 62 of 215
Field name Status Update on GI
Description
User action and values Deselected
Note
Page 63 of 215
Result
Control profile for delivery YA000001 is maintained.
2.1.2.8 Use
Creating JIT Customer
This step is to create JIT customer at the supplier side.
Procedure
Page 64 of 215
SAP ECC menu
Logistics Logistics Execution JIT Inbound Basic Data Maintain Customer
Page 65 of 215
Transaction code
JITV
Page 66 of 215
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:
Page 67 of 215
Field name JIT Customer Sold-to party Partner Descr Cust. time zone Usage Determ.Profile Sig.monitor active CallType MaintenanceMode SumJC Profile
Description
User action and values UCAR A-6701 1000 JAPAN S YA000001 Select Summarized JIT Call [D] Discrete Material /SumJC YA0000000001
Note
(or your personalized data)
Page 68 of 215
Field name Profile dely creatn
Description
User action and values YA000001
Note
Page 69 of 215
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:
Page 70 of 215
Stat. Info 0000 1200
Ext. Status VF VF VF
Page 71 of 215
Stat. Info 1400
Ext. Status VF
Page 72 of 215
10. Choose Maintain Lead Times from Dialog Structure:
Page 73 of 215
Field name CG Type Basis Time Ext. Status Days TimeShift
Description
User action and values Time of External Status Change VF 02:00:00
Note
Page 74 of 215
Field name Prelim.Run
Description
Note
Page 75 of 215
11. Choose Save. 12. Choose Maintain Destinations from Dialog Structure. 13. Choose New Entries. 14. Make the following entries :
Page 76 of 215
Field name Destination JIT Customer Unloading Point Assy Loc. DestText 1
Description
User action and values WSP3 UCAR Tor 10 YA0004
Note
Supply area
Page 77 of 215
Field name DestText 2
Description
Note
Page 78 of 215
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:
Page 79 of 215
Field name Comp.Grp Type Destination CG Material Call Control Plant
Description
User action and values WSP3 WSP3 A-67-2000_SUP YA01 1000
Note
Page 80 of 215
Field name CGText 1
Description
User action and values Component Group A67
Note
Page 81 of 215
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
Page 82 of 215
Transaction code
SM30 (Customizing Object V_TVAKZ)
Page 83 of 215
IMG menu
Sales and Distribution Sales Sales Documents Sales Documents Header Assign Sales Area To Sales Document Types
Page 84 of 215
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:
Page 85 of 215
Ref.S 1000
RefD 10
Div 10
SaTy LZJ
Page 86 of 215
4. Choose Save and then choose Back.
2.1.2.10 Use
Creating Scheduling Agreement LZJ
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
Page 87 of 215
SAP ECC menu
Logistics Logistics Execution JIT Inbound Environment Master Data Scheduling Agreement (SD) Create
Page 88 of 215
Transaction code
VA31
Page 89 of 215
2. On the Create Scheduling Agreement: Initial Screen, make the following entries:
Page 90 of 215
Field name Sched.Agreemt Type Sales Organization Distribution Channel Division Sales Office
Description
User action and values LZJ 1000 10 10 1000
Note
Page 91 of 215
Field name Sales Group
Description
Note
Page 92 of 215
3. Confirm your entries. 4. On the Create JIT Scheduling Agt: Overview screen, enter the following values:
Page 93 of 215
Field name JIT Scheduling.Agt. Sold-to party Ship-to Party
Description
User action and values 35006701 A-6701 A-6701
Note
Page 94 of 215
Field name PO Number
Description
Note
Page 95 of 215
5. On the Item Overview tab, enter the following entries:
Page 96 of 215
Field name Item Material Rounding Qty Customer Material Number PO Item
Description
User action and values 10 A-67-2000_SUP 0 A-67-2000_OEM 10
Note
Page 97 of 215
Field name Storage location
Description
Note
Page 98 of 215
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 Use
Creating Copy Control for Delivery
This activity copy controls.
Procedure
Page 99 of 215
Transaction code
VTLA
Page 100 of 215
IMG menu
Logistics Execution Shipping Copying Control Specify Copy Control for Deliveries
Page 101 of 215
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:
Page 102 of 215
Sales Doc Type LZJ
Delivery Type LF
ItemCat
Order requirements 101
Item Data 101
Item Ext. System 0
Business Data 2
Update doc flow X
+/-
LZN
Page 103 of 215
6. Choose Save. 7. Choose Back.
Result
Controls are copied.
2.2 Configuration in the OEM System

2.2.1 2.2.2 2.2.2.1 Use
The purpose of this activity is to creating the message record for forecast delivery schedule in MM Scheduling Agreement.
Master Data Maintain Configuration Creating Message Record for Forecast Delivery Schedule in MM Scheduling Agreement
Procedure
Page 104 of 215
SAP ECC menu
Logistics Materials Management Purchasing Master Data Messages Scheduling Agreement Delivery Schedule Create
Page 105 of 215
Transaction code
MN10
Page 106 of 215
2. On the Create Output Condition Records: Purch.SchAgrRelease screen, make the following entries:
Page 107 of 215
Field name Output type
Description
User action and values YAH1
Note
Page 108 of 215
3. Choose Key Combination. 4. Confirm the dialog box. 5. Make the following entries:
Page 109 of 215
Field name Purch Organization Vendor Funct Medium
Description
User action and values 1000 A-V6701 VN 6
Note
Page 110 of 215
Field name Date/Time
Description
Note
Page 111 of 215
6. Choose Save. 7. Choose Back and go to SAP Easy Access screen.
2.2.2.2 Use
Partner Profile, Only Basic Data
Partner profiles for EDI communication are created at the OEM side.
Procedure
Page 112 of 215
SAP ECC menu
Logistics Logistics Execution Internal Whse Processes Communication with External Systems ALE Administration Runtime Settings Partner Profiles
Page 113 of 215
Transaction code
WE20
Page 114 of 215
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:
Page 115 of 215
Field name Partner No.
Description
User action and values A-V6701
Note 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.
Page 116 of 215
5. On the right area of Partner profiles screen, select Post processing: permitted agent. 6. Make the following entries:
Page 117 of 215
Field name Ty.
Description Agent type
User action and values US
Note 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).
Page 118 of 215
Field name Lang.
Description Language of notification
User action and values EN
Note If an error occurs, SAPoffice notifies the permitted user in this language.
Page 119 of 215
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 Use
Partner Profile Outbox for DELFOR and SEQJIT
Outbound parameters in partner profiles are created at OEM side.
Procedure
Page 120 of 215
SAP ECC menu
Page 121 of 215
Transaction code
WE20
Page 122 of 215
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:
Page 123 of 215
Field name Partner Role
Description Partner function of sender
User action and values VN
Note 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.
Page 124 of 215
Field name Message type
Description
User action and values DELFOR
Note 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 ORDERS for purchase order data INVOIC for invoice data
Page 125 of 215
5. On the bottom area of the screen Partner profiles: Outbound parameters, select outbound options tab. 6. Make the following entries:
Page 126 of 215
Field name Receiver Port
Description
User action and values Z_AUTO
Note 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 is started immediately for each individual IDoc. 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.
Output Mode Basic type
Transfer IDoc immed. DELFOR02
Page 127 of 215
Field name Cancel Processing After Syntax Error
Description
User action and values X
Note 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
7. Choose Save. 8. Repeat steps 1-7 to make the following entries:
Page 129 of 215
Partn er No.
Partn. Type
Partner Role
Mess age Type SEQJ IT
Receiv er Port
Packet Size
IDoc Type
Transfe r IDoc Immed.
Cancel Processing After Syntax Error X
AV6701
LI
VN
Z_AUT O
SEQJ IT03
Page 130 of 215
Result
The message types DELFOR and SEQJIT are maintained for partner profile A-V6701.
2.2.2.4 Use
Partner Profiles Message Control for DELFOR and SEQJIT
Message Control of outbound parameters in partner profiles is created at OEM side.
Procedure
Page 131 of 215
SAP ECC menu
Page 132 of 215
Transaction code
WE20
Page 133 of 215
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.
Page 134 of 215
Field name Partner Role
Description
User action and values VN
Note
Page 135 of 215
Field name Message Type
Description
User action and values DELFOR
Note
Page 136 of 215
4. On the bottom area of the Partner profiles: Outbound parameters screen, select Message Control options tab. 5. Make the following entries:
Page 137 of 215
Field name Application
Description
User action and values EL
Note 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').
Page 138 of 215
Field name Process code
Description
User action and values ME14
Note 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
Page 139 of 215
6. Choose Save. 7. Repeat steps 1-6 to make the following entries:
Page 140 of 215
Partner No A-V6701
Partn.Type LI
Partner Role VN
Message Type SEQJIT
Application PA
Message Type OJIT
Process Code SJCL
Page 141 of 215
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 Procedure
Defining JIT Call Control
Step 1: Define Processing Status 1. Access the activity using one of the following navigation options:
Page 142 of 215
Transaction code
SPRO
Page 143 of 215
IMG menu
Logistics Execution JIT Inbound Call Control Define External Status and Internal Processing Status
Page 144 of 215
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:
Page 145 of 215
ProcStat 0000 1000 1400 1600 1700
Text Call not saved/deleted JIT-call created JIT JIT-call modified JIT JITOUT MAB: ASN created JIT MSBASN JITOUT MAB: GR posted JIT MSB JITOUT MAB: JC finished JIT MSBJC
Page 146 of 215
ProcStat 7000
Text Delivery created
Page 147 of 215
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:
Page 148 of 215
Transaction code
SPRO
Page 149 of 215
IMG menu
Logistics Execution JIT Outbound Call Control Define Call Control
Page 150 of 215
2. Choose New Entries. 3. On the New Entries: Overview of Added Entries screen, make the following entries:
Page 151 of 215
Field name Control Call Ctrl Short Text
Description
User action and values YA01 Summarized JIT call control
Note
Page 152 of 215
Field name Logging Active
Description
User action and values Deselect
Note
Page 153 of 215
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.
Page 154 of 215
PrSt.Curr 0000 0000 0000 1400 1600 1700
Action OCRE OMOD OSDD OSHP OGRE OFIN OARC
Prc.st.new 0000 0000 1400 1400 1600 1700
Page 155 of 215
PrSt.Curr 1700
Action OREO
Prc.st.new
Page 156 of 215
Result
The call control YA01 is maintained.
2.2.2.6 Use
Creating JIT Call Profile
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
Page 157 of 215
Transaction code
SPRO
Page 158 of 215
IMG menu
Logistic Execution JIT Outbound Control Profiles Define JIT Call Profile
Page 159 of 215
2. Choose New Entries 3. On the New Entries: Details of Added Entries screen, make the following entries:
Page 160 of 215
Field name JC profile JIT call profil JIT Call type Partner Role JC Summary Time definition Call Control
Description
User action and values YA01 SumJC (Outbound) SumJC ( ) S VN Summary by plant, unloading point YA01
Note
Page 161 of 215
Field name Messg Det. Usage
Description
User action and values Message Determination Required
Note
Page 162 of 215
4. Choose Save (Ctrl + S). 5. Choose Back (F3).
Result
The summarized JIT call profile ZJC1 has been created.
2.2.2.7 Use
Creating Condition: JIT Call
The purpose of this activity is to create the message condition for JIT calls.
Procedure
Page 163 of 215
SAP ECC menu
Logistics Production KANBAN JIT Call Message Conditions Create
Page 164 of 215
Transaction code
PJNK1
Page 165 of 215
2. On the Create Output - Condition Record: JIT Call screen, make the following entries:
Page 166 of 215
Field name Output Type
Description
User action and values OJIT
Note
Page 167 of 215
3. Choose Key Combination (Enter). 4. On the key Combination screen, select following checkbox:
Page 168 of 215
Field name Plant/JC Profile/vendor
Description
Note
Page 169 of 215
5. Choose Enter. 6. On the Create Condition Records (Outbound JIT-Call):Fast Entry screen, select the following entry:
Page 170 of 215
Field name Plant JC Profile Vendor Funct Medium
Description
User action and values 1000 YA01 A-V6701
Note
Partner Function
VN 6 EDI
Page 171 of 215
Field name Date/Time
Description
Note
Page 172 of 215
7. Choose Save (Ctrl + S).
Result
The message condition for summarized JIT call OJIT for A-V6701 has been created.
2.2.2.8 Use
Creating MM Scheduling Agreement
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
Page 173 of 215
SAP ECC menu
Logistics Material Management Purchasing Master Data Subsequent Settlement Vendor Rebate Arrangement Environment Vendor Environment Outline agreement Create
Page 174 of 215
Transaction code
ME31
Page 175 of 215
2. On the Create Contract: Initial Screen, make the following entries:
Page 176 of 215
Field name Vendor Agreement Type Agreement Organizational Data Purch. Organization Purchasing Group Default Data for Items Plant
Description
User action and values A-V6701 LPA 5600006701 10000 100 1000
Note
Page 177 of 215
Field name Storage Location
Description
Note
Page 178 of 215
3. Choose Continue (Enter). 4. On the Create Scheduling Agreement: Header Data screen, make the following entries:
Page 179 of 215
Field name Validity end Invoicing party
Description
User action and values For example: 2099.12.31 A-V6701
Note
Page 180 of 215
Field name Suppl. vendor
Description
User action and values A-V6701
Note
Page 181 of 215
5. On the Create Scheduling Agreement: Item Overview screen, make the following entries:
Page 182 of 215
Field name Item Material Target Quantity
Description
User action and values 10 A-67-2000_OEM 1000000
Note
Page 183 of 215
Field name Net Price
Description
Note
Page 184 of 215
6. Select the item and choose Item Details. 7. On the Display Scheduling Agreement: Item 0010 screen, make the following entries:
Page 185 of 215
Field name Tax Code
Description
User action and values V1
Note
Page 186 of 215
8. Choose Additional data and make the following entries:
Page 187 of 215
Field name Kanban Indicat.
Description
User action and values Z
Note
Page 188 of 215
Field name Creation profile
Description
Note
Page 189 of 215
9. Choose Save.
Result
The scheduling agreement 5600006701 with type LPA has been created.
2.2.2.9 Use
Defining Replenishment Strategies for External Procurement
The purpose of this activity is to define replenishment strategies for external procurement.
Procedure
Page 190 of 215
Transaction code
SPRO
Page 191 of 215
IMG menu
Logistic Execution JIT Outbound Summarized JIT Call Define Replenishment Strategies For External Procurement
Page 192 of 215
2. On the Change View Replenishment Strategy: Ex. Procurement for SumJC: Over screen, select following entry:
Page 193 of 215
Field name Plant Ext. Procurement.
Description
User action and values 1000 YA01
Note
Page 194 of 215
Field name Replenishment Strategy Description
Description
User action and values Rep. Strategy: Ext. Proc. for Sum. JC JC
Note
Page 195 of 215
3. Choose Details. 4. On the Change View Replenishment Strategy: Ex. Procurement for SumJC : Deta screen, make the following entries:
Page 196 of 215
Field name Trans.Type Variable Source Use PIs Ctrl Cycle Card
Description
User action and values 101 X No functional use, packing instruction is a commentary CONTROLCYCLE
Note
Page 197 of 215
Field name Print Function
Description
User action and values PK_CONTROLCYCLE_PRINT
Note
Page 198 of 215
5. Choose Save (Ctrl + S). 6. Choose Back (F3).
Result
The external procurement strategy YA01 is maintained.
2.2.2.10 Use
Manual Step: Creating Control Cycle
The control cycle is required when you create summarized JIT call.
Procedure
Page 199 of 215
SAP ECC menu
Logistics Production KANBAN Control Cycle Control Cycle Maintenance
Page 200 of 215
Transaction code
PKMC
Page 201 of 215
2. On the Control Cycle Maintenance: Display screen, make the following entries and choose Data Selection (F8).
Page 202 of 215
Field name Plant
Description
Note
Page 203 of 215
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).
Page 204 of 215
Field name Material
Description
User action and values A-67-2000_OEM
Note
Page 205 of 215
Field name Supply Area
Description
Note
Page 206 of 215
6. On the Control Cycle Maintenance: Change screen, make the following entries.
Page 207 of 215
Field name Call Item Qty No.Load Carrier
Description
User action and values 10 1
Note
Page 208 of 215
Field name Ext. Procurement
Description
Note
Page 209 of 215
7. Choose Flow Control Tab page and make the following entries:
Page 210 of 215
Field name JIT call Profile
Description
Note
Page 211 of 215
8. Choose Enter. 9. Choose External Procurement tab page and make the following entries:
Page 212 of 215
Field name Agreement
Description
Note
Page 213 of 215
Field name
Description Item
Note
Page 214 of 215
10. Choose Enter and Save.
2.2.2.11 Use
Maintaining Source List
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 Transaction code Logistic Logistics Execution JIT Outbound Environment Master Data Maintain Source List ME01
2. On the Maintain Source List: Initial Screen, make the following entries: Field name Material Plant 3. Choose Enter. 4. On the Maintain Source List: Overview screen, make the following entries: Field name Valid from Valid to Vendor Porg Agmt Item Fix MRP 5. Choose Save. 6. Choose Back. Description User action and values Today For example: 2099.12.31 A-V6701 1000 5600006701 10 X 2 Note Description User action and values A-67-2000_OEM 1000 Note
Result
Purchase Source List for material A-67-2000_OEM is created.
Page 215 of 215

B A67 Scen ConfigGuide Scheduling Agreement With Summarized JIT Call

Enviado por

Dados do documento

Descrição original:

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

B A67 Scen ConfigGuide Scheduling Agreement With Summarized JIT Call

Enviado por

Direitos autorais:

Formatos disponíveis

AutoEdge

EHP4 for SAP ERP 6.0 March 2011 English

Scheduling Agreement with Summarized JIT Call (A67)

Building Block Configuration Guide

A KPIT Cummins Company

111 Woodmere Road Suite 200 Folsom, CA 95630 888-985-0301 916-985-0300

2011 Sparta Consulting

Scheduling Agreement with Summarized JIT Call 1 Purpose

2.1.1.1.1 Maintaining Partner Description in Customer Master Data Use

2011 Sparta Consulting

SAP ECC menu

2011 Sparta Consulting

2011 Sparta Consulting

2011 Sparta Consulting

Field name Customer Sales Organization Distribution Channel

User action and values A-6701 1000 10

2011 Sparta Consulting

Field name Division

User action and values 10

2011 Sparta Consulting

2011 Sparta Consulting

Field name Partner Functions

User action and values

2011 Sparta Consulting

Field name Partner description

User action and values 1000

2011 Sparta Consulting

5. Choose Save. 6. Choose Back.

2.1.2 2.1.2.1 Use

Other Settings Creating Pricing Condition

The purpose of this activity is to create condition records at supplier side.

2011 Sparta Consulting

SAP ECC menu

2011 Sparta Consulting

2011 Sparta Consulting

2011 Sparta Consulting

Field name Sales Organization

User action and values 1000

2011 Sparta Consulting

Field name Distribution Channel

User action and values 10

Note Direct Sales

2011 Sparta Consulting

2011 Sparta Consulting

2011 Sparta Consulting

2011 Sparta Consulting

Determining Sold-To Party

2011 Sparta Consulting

2011 Sparta Consulting

2011 Sparta Consulting

2. Choose New Entries, make the following entries:

2011 Sparta Consulting

Partner desc 1000

Sold-to party A-6701

2011 Sparta Consulting

Defining Special Features for Delivery Schedules

2011 Sparta Consulting

2011 Sparta Consulting

2011 Sparta Consulting

2. Choose New Entries, make the following entries:

2011 Sparta Consulting

Sold-To Party A-6701

2011 Sparta Consulting