2014-11-11 - 10735 - Spec - Program to create call offs with ref to Contracts for Japan cust. portal orders #JapanSD #APAC #OrderEntry #JapanABAP

SPECIFICATIONS

10735 - Spec - Program to create call offs w/ref to Contracts for Japan customer portal orders

Purpose

---

The business needs to reserve inventory for accounts. This is done today in contracts.

• The challenge is the customer does not specify the contract in the call-off and an order will include contract and non-contract items

Goals

• Use contracts to reserve inventory for a customer.
• Allow mixed orders with contract and non-contract materials.
• Need to create an order confirmation for uploading into the customer’s portal.

Create call offs with or w/o reference to contract items from input file.

Admin Info

---

Purpose	Create Call offs with reference to contract item using data from file as input
Requested By	Jack Mehltretter
Spec Created By	Dan Gupta/Surya Basa
Spec Created Date	11/11/2014
Spec QA by	Surya Basa
Objects	ZSD_JPN_ORD_CALL_OFF Z_SO_LOAD_AUDIT ZJPN_CALL_OFF V_TVLS V_TVAG /AFS/TVAG_V V_T176 J_3AT176_V ZJEDI ZJCALL
Document Status	Complete

Estimates

---

Sl.No	Activity	Estimation in Hours
1	Research	08
2	Documentation	10
3	Development/ Config	40
4	Unit test in DEV	80
5	Unit test in QUA	50
6	Other activity
	TOTAL	188

References

---

Prior Tickets

[Provide links of prior associated Spec / Break Fix BOSS document(s)]

NA

Documents

[Attach any document(s) received for the requirement(s)]

Japan Order Upload.pptx

Spec Changes

---

[List the changes made to program after the approval of the original requirement along with the Date on which the change request was received and the name of the initiator]

Sl.	Change Details	Requested By	Requested On	Notes if any
1	Add new PO type (JPC) as an identifier on the contract that should be ignored by the program in the open contract selection	Daniel Brennan	11/18/2014	NA
2	Check open contract quantity for each sales order at item level and create call off with reference to contract if the item status is open.	Abe Maritime	11/24/2014	Scenario JP-000013B2 should create a standard order with reference and w/o delivery block
3	Update program to create call offs using standard IDOCs - ORDERS (ROC format)	Abe Maritime	06/09/2015	NA

Functional Requirement

---

Purpose/WHY:

[Explain the purpose of the project and the reason why this requirement has come]

There are currently four key customers that upload their orders to a customer portal and New Era downloads the details from the file which is a pre-defined format that is unique to each customer. A custom program needs to be developed to load this file as a contract call-off(s) into SAP. The program will identify the appropriate existing contract (if any) for this purpose.

In Scope/Assumptions

[List the activities to be included in scope]

• The custom program is restricted to Japan (SA-3200/10/00) and to order types ZOR.
• It is assumed that the input file format will be the same for all customers. A prior process (using GIS) will convert the customer portal data into this format
• The order created in SAP can contain call-off lines from multiple valid contracts as well as lines with no reference to a contract.
• If multiple contracts exist, then the order will go into delivery hold for customer service to resolve.

Out of Scope:

[Out of scope activities]
The program is not global and other document types not mentioned above are not handled in the program.

Solution Summary

---

[Discuss this section with Requester and get approval prior to beginning work]

Process and Configuration
The Business process is as shown in the flowchart above. SAP impact and configuration to support the process is listed below:

• Multiple Order Call-Offs in same Order: Standard SAP will be used. The contract used will be seen in the reference doc field of the Sales Order line.
• Order Lines without Contracts: These too will be created in the same order
• Reject Code: A new reject code is required to be created to indicate valid multiple contracts are found for the customer and material
  • This will prevent delivery from being created
  • User will have to manually remove this reject code and block to create the delivery
  • Valid contract: Call-off's requested delivery date is between [Contract Validity Start and Contract Validity End] and open quantity >0
  • If multiple valid contracts found, then the one with earliest Request Date will be defaulted in the order
• PO Type: New PO type Z* to be created to indicate call offs created via GIS->Upload program. The same should be mapped as default in GIS.

Program
A custom program will be developed to process a flat file (CSV) with customer order data received from the portal. A standard BAPI will be called within this program to create orders in SAP.

Program will create a csv file similar to the ROC order file; standard IDOC type ORDERS will be used to create orders via GIS.


Note: Each combination of [Sold-To+Ship-To+ PO] will generate a unique Sales Order in SAP.

The input file will be undergo basic validation for missing or invalid data (e.g. invalid customer/material number/dates).
Beyond that, any extensive validation will be done by the standard SAP logic when the order is posted via the BAPI in SAP.

Validations will be done by the standard IDOCs and the programs will not carry out any validations.


Any Input records failing basic validation or BAPI errors will stop the entire order from being be loaded in SAP. The records for this order will be loaded into a custom ZTable for users to view the error.

• Users will then need to create a new input file with corrections to re-process failed orders.

Standard IDOC errors created via EDI (ORDERS) will not be shown in the Ztable.

Test Plan
[List test scenarios/cases to be executed here]

PO #	Sold to	Ship to	Material #	Grid #	ATP Check	JAN #	Load file Qty	Ref. Contract #	Contract	Contract Allocation	Inventory	Expected Results
JP-00001	Call offs should be created if there's a valid open contract and w/o reference when not
	1016242	1016242	11089406	678	Z2	4549518154547	1	40006861	Single Contract	Full allocation	Available	Order line should be loaded with contract reference
				700	Z2	4549518154554	1	40006861	Single Contract	Full allocation	Available	Order line should be loaded with contract reference
			11089411	678	Z3	4549518155148	1		No contract		Available	Order line should be loaded w/o contract reference
				700	Z3	4549518155155	1		No contract		Available	Order line should be loaded w/o contract reference
			11089407	678	Z2	4549518154646	1	40006861	Single Contract	Full allocation	Available	Order line should be loaded with contract reference
				700	Z2	4549518154653	1	40006861	Single Contract	Full allocation	Available	Order line should be loaded with contract reference
JP-00002	Multiple Contract References exist with Z2 and Z3 materials with free available inventory; orders should be created with reference if there's a match and w/o if not and consuming inventory from free available
	1016242	2065915	11089406	718	Z2	4549518154585	1	40006865	Single Contract	Not allocation	Not available	Order line should be loaded with contract reference
			11089411	678	Z3	4549518155148	1		No contract		Available	Order line should be loaded w/o contract reference
				700	Z3	4549518155155	1		No contract		Available	Order line should be loaded w/o contract reference
			11089407	678	Z2	4549518154646	1	40006861	Single Contract	Full allocation	Available	Order line should be loaded with contract reference
				700	Z2	4549518154653	1	40006861	Single Contract	Full allocation	Available	Order line should be loaded with contract reference
JP-00003	Multiple Contract References exist and Z3 behaviour when there's no free available inventory and when both valid open contracts have the same validity period
	1016242	1016242	11089412	678	Z2	4549518155049	1	40006876, 40006877	Multiple Contract	Full allocation	Available	Order line should be loaded with first valid Contract & with delivery block and reject reason
				700	Z2	4549518155056	1	40006876, 40006877	Multiple Contract	Full allocation	Available	Order line should be loaded with 1st Contract # & reject reason
			11089411	718	Z3	4549518155186	1		No contract		Not available	Order line should be loaded with J0 rejection reason because of no inventory
JP-00004	Check behaviour when a line has RDD outside the validity period of open contracts
	1016242	1016242	11089406	678	Z2	4549518154547	1	40006861	Single Contract	Full allocation	Available	Order line should be loaded with contract reference.
				712	Z2	4549518154561	1	40006876, 40006877	Multiple Contract	Full allocation	Available	Order line should be loaded with reference to 1st valid contract & with delivery block and reject reason
			11089411	718	Z3	4549518155186	1		No contract		Not available	Order line should be loaded with J0 rejection reason because of no inventory and w/o contract reference.
				700	Z3	4549518155155	1		No contract		Available	Order line should be loaded without contract reference.
			11089407	678	Z2	4549518154646	1	40006861	Single Contract	Full allocation	Available	Order line should be loaded with contract reference.
				712	Z2	4549518154660	1	40006881	Exists but not in Req Del Dt	Full allocation	Available	Order line should be loaded without any contract reference
JP-00001	Duplicate order or load file with PO# JP-00001 again (same combination of SP, SH and PO #)
	1016242	1016242	11089406	678	Z2	4549518154547	1	40006861	Single Contract	Full allocation	Available	Order line should be loaded with reference to contract and with delivery block
				700	Z2	4549518154554	1	40006861	Single Contract	Full allocation	Available	Order line should be loaded with reference to contract and with delivery block
			11089411	678	Z3	4549518155148	1		No contract		Available	Order line should be loaded w/o reference to contract and with delivery block
				700	Z3	4549518155155	1		No contract		Available	Order line should be loaded w/o reference to contract and with delivery block
			11089407	678	Z2	4549518154646	1	40006861	Single Contract	Full allocation	Available	Order line should be loaded with reference to contract and with delivery block
				700	Z2	4549518154653	1	40006861	Single Contract	Full allocation	Available	Order line should be loaded with reference to contract and with delivery block
NA	PO # blank in input file for a combination of SP, SH, PO #
	1016242	2065915	11089406	678	Z2	4549518154547	1	40006861	Single Contract	Full allocation	Available	Entire order should not be loaded and error message should be logged into Zerror table - ZJPN_CALL_OFF
				700	Z2	4549518154554	1	40006861	Single Contract	Full allocation	Available
			11089411	678	Z3	4549518155148	1		No contract		Available
				700	Z3	4549518155155	1		No contract		Available
JP-00007	Sold To blank in input file for a combination of SP, SH, PO #
	NA	1016242	11089406	678	Z2	4549518154547	1	40006861	Single Contract	Full allocation	Available	Entire order should not be loaded and error message should be logged into Zerror table - ZJPN_CALL_OFF
				700	Z2	4549518154554	1	40006861	Single Contract	Full allocation	Available
			11089411	678	Z3	4549518155148	1		No contract		Available
				700	Z3	4549518155155	1		No contract		Available
JP-00008	Ship To blank in input file for a combination of SP, SH, PO#
	1016242	NA	11089406	678	Z2	4549518154547	1	40006861	Single Contract	Full allocation	Available	Entire order should not be loaded and error message should be logged into Zerror table - ZJPN_CALL_OFF
				700	Z2	4549518154554	1	40006861	Single Contract	Full allocation	Available
			11089411	678	Z3	4549518155148	1		No contract		Available
				700	Z3	4549518155155	1		No contract		Available
JP-00009	RDD blank or invalid in input file for a combination of SP, SH, PO #
	1016242	1016242	11089406	678	Z2	4549518154547	1	40006861	Single Contract	Full allocation	Available	Entire order should not be loaded and error message should be logged into Zerror table - ZJPN_CALL_OFF
				700	Z2	4549518154554	1	40006861	Single Contract	Full allocation	Available
			11089411	678	Z3	4549518155148	1		No contract		Available
				700	Z3	4549518155155	1		No contract		Available
JP-000010	Cancel date blank or Invalid in input file for a combination of SP, SH, PO #
	1016242	2065915	11089406	678	Z2	4549518154547	1	40006861	Single Contract	Full allocation	Available	Entire order should not be loaded and error message should be logged into Zerror table - ZJPN_CALL_OFF
				700	Z2	4549518154554	1	40006861	Single Contract	Full allocation	Available
			11089411	678	Z3	4549518155148	1		No contract		Available
				700	Z3	4549518155155	1		No contract		Available
JP-000011	Quantity value ZERO or blank in input file for a combination of SP, SH, PO #
	1016242	1016242	11089406	678	Z2	4549518154547	0	40006861	Single Contract	Full allocation	Available	Entire order should not be loaded and error message should be logged into Zerror table - ZJPN_CALL_OFF
				700	Z2	4549518154554	0	40006861	Single Contract	Full allocation	Available
			11089411	678	Z3	4549518155148	0		No contract		Available
				700	Z3	4549518155155	0		No contract		Available
JP-000012	Invalid JAN ID/ Blank in file
	1016242	1016242	11089411	678	Z3	4549518155148	1		No contract		Available	Entire order should not be loaded and error message should be logged into Zerror table - ZJPN_CALL_OFF
				700	Z3	4549518155155	1		No contract		Available
	When Contract has 1 size with open qty 10 available and input the Load file for 2 call offs for same size.
JP-000013A	1016242	1016242	11089409	678	Z2	4549518154844	10	40006866	Single Contract	Full allocation	Available	Call off should be loaded with contract reference
JP-000013B	1016242	1016242	11089409	678	Z2	4549518154844	5		No contract		Available	Sales order should be loaded w/o reference and inventory from free available should be consumed
	When Contract has 2 sizes (738, 758) with 10 open qty available for each and two call offs for same size 738
JP-000013B1	1016242	1016242	11089409	738	Z2	4549518154905	10	40006879	Single Contract	Full allocation	Available	1st call off should be created with contract reference and open contract quantity should be consumed for size 738
JP-000013B2	1016242	1016242	11089409	738	Z2	4549518154905	10	40006879	Single Contract	Full allocation	Available	2nd call off should be created with contract reference consuming inventory from free available w/o delivery block
JP-000014	Valid contract status open followed by call off quantity greater than open quantity for a combination of SP, SH, PO #
	1016242	1016242	11089409	700	Z2	4549518154851	15	40006867	Single Contract	Full Allocation	Available	Entire order should be loaded with reference to the contract with the total quantity
JP-000015	Single valid open contract with PO Type JPC
	1016242	1016242	11089409	712	Z2	4549518154868	1	40006868 - JPC	Single Contract	Full Allocation	Available	Order line should be loaded w/o reference to contract.
JP-000016	2 Contracts with PO type JPC & non JPC for the same JAN ID.
	1016242	1016242	11089409	714	Z2	4549518154875	1	40006869 - JPC, 40006870	Multiple Contract	Full Allocation	Available	Order line should be loaded with reference to Contract with PO type non-JPC.
JP-000017	4 Open Contracts for the same JAN ID. And 1st & 2nd contract with PO type JPC and rest with non-JPC PO type.
	1016242	1016242	11089409	718	Z2	4549518154882	1	40006871 - JPC, 40006872 - JPC, 40006873, 40006874	Multiple Contract	Full Allocation	Available	Order line should be loaded with reference to earliest Contract w/o PO type JPC and with ZJ block at header & rejection at item level.
JPT-11	When contract has two sizes with open quantity 10 each and w/o free inventory followed by two call offs
	1016242	1016242	11089412	712	Z2	4549518155063	15	40006883	Single	Full Allocation	Not Available	Order line should be loaded with referece to contract
JPT-12	1016242	1016242	11089412	712	Z2	4549518155063	15	40006883	Single	Full Allocation	Not Available	Order line should be loaded with referece to contract

New Test Plan for IDOCs

Scenario	Scenario Description	ATP Check Z2=with Lead Time Z3= w/o Lead Time	Contract	Inventory	Expected Results
1	Multiple call-offs in input file, but each material has only 1 open valid contract; inventory is available				Call offs should be created referencing the ref. contract
		Z2	Single Contract	Available	Order line should be loaded with contract reference
		Z2	Single Contract	Available	Order line should be loaded with contract reference
		Z3	Single Contract	Available	Order line should be loaded with contract reference
		Z3	Single Contract	Available	Order line should be loaded with contract reference
		Z2	Single Contract	Available	Order line should be loaded with contract reference
		Z2	Single Contract	Available	Order line should be loaded with contract reference
2	Multiple call-offs in input file, each material can have either 1 open valid contract or no Contract; Inventory may or may not be available				Call offs should be created with reference where available; otherwise create standalone SO line.
		Z2	Single Contract	Available	Order line should be loaded with contract reference
		Z3	Single Contract	Available	Order line should be loaded with contract reference
		Z3	Single Contract	Not available	Order line should be loaded with J0 rejection reason
		Z3	No contract	Not available	Order line should be loaded w/o contract reference with J0
		Z2	No contract	Not available	Order line should be loaded w/o contract reference
		Z2	No contract	Available	Order line should be loaded w/o contract reference
3	Multiple call-offs in input file, each material has multiple open valid Contracts or no contract; Inventory available				Call offs should be created referencing earliest RDD contract with ZJ delivery block and ZJ rejection
		Z2	Multiple Contract	Available	Order line should be loaded with first valid Contract & with delivery block and reject reason
		Z2	Multiple Contract	Available	Order line should be loaded with first valid Contract & with delivery block and reject reason
		Z3	Multiple Contract	Available	Order line should be loaded with first valid Contract & with delivery block and reject reason
4	Some materials have valid open contracts but RDD is outside the contract validity dates; Inventory may or may not be available				Materials with valid open contracts loaded with ref. Z2 materials w/o valid open contracts loaded w/o ref. Z3 materials w/o valid open contracts loaded w/J0 rej. Code
		Z2	Single Contract	Available	Order line should be loaded with contract reference.
		Z2	Multiple Contract	Available	Order line should be loaded with reference to 1st valid contract & with delivery block and reject reason
		Z3	No contract	Not available	Order line should be loaded with J0 rejection reason because of no inventory and w/o contract reference.
		Z3	No contract	Available	Order line should be loaded without contract reference.
		Z2	Single Contract	Available	Order line should be loaded with contract reference.
		Z2	Exists but not in Req Del Dt	Available	Order line should be loaded without any contract reference
5	DUPLICATE ORDERS: If sales order already in system with (Sold-To+Ship-To+PO ); then load this order but put on delivery block on Order				Call offs should be created with reference where available and w/o if not and with delivery block
		Z2	Single Contract	Available	Order line should be loaded with reference to contract and with delivery block
		Z2	Single Contract	Available	Order line should be loaded with reference to contract and with delivery block
		Z3	No contract	Available	Order line should be loaded w/o reference to contract and with delivery block
		Z3	No contract	Available	Order line should be loaded w/o reference to contract and with delivery block
		Z2	Single Contract	Available	Order line should be loaded with reference to contract and with delivery block
		Z2	Single Contract	Available	Order line should be loaded with reference to contract and with delivery block
		Z2	Multiple Contract	Available	Order line should be loaded with reference to 1st valid contract & with delivery block and reject reason
6	Multiple call-offs exist in the input file for a contract line with SINGLE size. The first call-off consumes the entire contract quantity. Subsequent call-offs should be loaded in sales order w/o ref.				Call offs should be created with reference for available and w/o reference where not available
		Z2	Single Contract	Available	Call off should be loaded with contract reference
		Z2	No contract	Available	Sales order should be loaded w/o reference and inventory from free available should be consumed
7	Multiple call-offs exist in the input file for a contract line with MULTIPLE sizes. The first call-off consumes ONE size fully but the contract line is still open due to other sizes. Subsequent call-offs for the consumed size should be loaded in sales order w/o ref.				Call offs should be created with reference for open lines and w/o reference if no-open quantity on contract
		Z2	Single Contract	Available	1st call off should be created with contract reference and open contract quantity should be consumed for size 738
		Z2	Single Contract	Available	2nd call off should NOT be created with contract reference consuming inventory from free available w/o delivery block
8	Requested Qty is greater than open contract quantity; inventory available				Order is loaded w/reference and open contact Excess quantity should be loaded w/o reference
		Z2	Single Contract	Available	Entire order should be loaded with reference to the contract with the total quantity
	Do not reference contracts with PO Type =JPC				Load order w/o reference to PO
		Z2	Single Contract	Available	Order line should be loaded w/o reference to contract.
9	Multiple contracts for same material - one PO Type = JPC and the other non-JPC. Call-offs will be created w/ref to non-JPC contract.				Call-offs will be created w/ref to non-JPC contract.
		Z2	Multiple Contract	Available	Order line should be loaded with reference to Contract with PO type non-JPC.
10	Several (at least 4) open contracts for the same material. Call-offs will be created w/ref to earliest non-JPC contract.
		Z2	Multiple Contract	Available	Order line should be loaded with reference to earliest Contract w/o PO type JPC and with ZJ block at header & rejection at item level.
11	Requested Qty is greater than open contract quantity; inventory not available				Order should load w/ref for open qty and w/o ref for excess. ATP should use Lead time
		Z2	Single	Not Available	Order line should be loaded with referece to contract
12	Input Validation: BLANK PO - Do not load records with blank PO; log errors				Call offs should not be loaded; log error
		Z2	Single Contract	Available	Entire order should not be loaded and error message should be logged into Zerror table - ZJPN_CALL_OFF
		Z2	Single Contract	Available
		Z3	No contract	Available
		Z3	No contract	Available
13	Input Validation: BLANK SOLD TO - Do not load records with blank Sold-To; log errors				Call offs should not be loaded; log error
		Z2	Single Contract	Available	Entire order should not be loaded and error message should be logged into Zerror table - ZJPN_CALL_OFF
		Z2	Single Contract	Available
		Z3	No contract	Available
		Z3	No contract	Available
14	Input Validation: BLANK SHIP TO - Do not load records with blank Ship-To; log errors				Call offs should not be loaded; log error
		Z2	Single Contract	Available	Entire order should not be loaded and error message should be logged into Zerror table - ZJPN_CALL_OFF
		Z2	Single Contract	Available
		Z3	No contract	Available
		Z3	No contract	Available
15	Input Validation: Do not load if RDD blank or invalid; log errors				Call offs should not be loaded; log error
		Z2	Single Contract	Available	Entire order should not be loaded and error message should be logged into Zerror table - ZJPN_CALL_OFF
		Z2	Single Contract	Available
		Z3	No contract	Available
		Z3	No contract	Available
16	Input Validation: Do not load if Cancel date blank or invalid; log errors				Call offs should not be loaded; log error
		Z2	Single Contract	Available	Entire order should not be loaded and error message should be logged into Zerror table - ZJPN_CALL_OFF
		Z2	Single Contract	Available
		Z3	No contract	Available
		Z3	No contract	Available
17	Input Validation: Do not load if Quantity value ZERO or blank; log errors				Call offs should not be loaded; log error
		Z2	Single Contract	Available	Entire order should not be loaded and error message should be logged into Zerror table - ZJPN_CALL_OFF
		Z2	Single Contract	Available
		Z3	No contract	Available
		Z3	No contract	Available
18	Input Validation: Do not load if Invalid JAN ID/ Blank; log errors				Call offs should not be loaded; log error
		Z3	No contract	Available	Entire order should not be loaded and error message should be logged into Zerror table - ZJPN_CALL_OFF
		Z3	No contract	Available
19	EDI validations incl recently for Japan (e.g. Requested or Cancel date is in past) - should these be used in this process?				TBD

Solution Details

---

[Provide complete technical details for configuration or programming here]

Customization Details

• Create new delivery block ZJ (Japan Call Off Block) under the menu path -

SPRO>Logistics Execution>Shipping>Deliveries>Define reasons for blocking in shipping

• Create new rejected code ZJ (Japan Call off) under the menu path -

SPRO>Sales & Distribution>Sales>Sales Document Item>Define reasons for rejection

• Create new PO Type JPC (Japan Contract) under the menu path -

SPRO>Sales & Distribution>Sales>Sales Documents>Sales Document Header>Define PO Types

• Assign PO type - JCP to the combination of sales org+sales document type (3200+ZCQ) under the menu path-

SPRO>Sales & Distribution>Sales>Sales Documents>Sales Document Header>Assign Ordering Types


Custom Program Details

Tcode: ZJEDI - Japan EDI Orders

Program Select Options

• File source location (App server or Desktop)
• File name Radio button(specific name or all)

Source File processing logic

• Read all files in source location and process one at a time

For each input file

• Sort data by Shipto+Soldto+PO (= the sap order)
• Group records by sap order
• Retrieve Contract and Material ID for all lines in order
• Validate each record in this order (per "Data Validation" section below). If any error found,
  • then entire order is flagged as error and records copied to Zerror table with error message on relevant lines
  • update program exec log = "Soldto+ShipTo+PO" failed - see error table

• If multiple contracts are found with different requested delivery dates then select the contract that has the earliest date. In case of a tie, select the first contract in order of ascending occurrence. Also add rejection code to this line to alert customer service of multiple contracts
• If no errors, then BAPI (ZSD_JPN_ORD_CALL_OFF) is called to create SAP order
• If BAPI fails, then
  • entire order is flagged as error and records added to zerror table with error messag
  • update program exec log = "Soldto+Shipto+PO" failed - see error table

• If BAPI successful, then update program exec log = " Sales Order 9999" created for "Soldto+shipto+PO"
• Archive processed file into some location ( delete & move)

File Format and Data mapping

The file should contain the data in the format shown below

Bill-To

Ship-To

Cust PO#

Requested Delv.Dt

Cancel Dt

JAN ID

Qty

• Data Mapping:
  All fields will be transferred in SAP as received except
  • Material ID
    • Source file will have Jan code. Lookup SAP material ID.
  • Contract
    • Source file will not have contract number
    • Find valid contract for sold-to & JAN combination where Order Request date is within contract validity date
    • Contract Open quantity > 0
    • If multiple contracts found, then
      • Put reject code on line and load the line with the contract # as mentioned above into the order.
      • Put delivery block at header level (create new delivery block)

• ROC file format with out Contract Number

Field Name	Format	Mapping	Comments
Header Record	There is no Fixed length, fields are separated by '~' and data type character
Record Indicator		H
Internet Order Number		Not Used	This is generated in ROC System
Sales Organization		Always 3200
Distribution Channel		Always 10
Division		Always 00
Cust Id(Sold To)		From File
Customer PO Number		From File
Ship To		From File
Sales Person		Not Used
Order Date	Date(MM/DD/YYYY) + Time Hardcoded (12:00:00 AM)	Current Date + Time 12 AM
Ship By Date	Date(MM/DD/YYYY) + Time Hardcoded (12:00:00 AM)	From File + Time 12 AM
Cancel date	Date(MM/DD/YYYY) + Time Hardcoded (12:00:00 AM)	From File + Time 12 AM
Payment Terms		Not Used( Not Necessary, System will determine the Payment Term)
Carrier Service		Not Used
Blank Field		Blank
Customer Group		Not Used ( Not Necessary, System will determine automatically)
Terms Override		Not Used
Dealer Override		Not Used
Contact Persons Phone		Not Used
Contact Persons Fax		Not Used
Contact Persons Email		Not Used
Hard Coded Value		Using Null	GLPR or DOMA OR NULL
Item Record
Record Indicator		L
Internet Order Number		Not Used	This is generated in ROC System
Cust Id(Sold To)		From File
Customer PO Number		From File
Seq No		Not Used	Some sequence number generated in ROC System
UPC Id		From File
Hard Coded Value		Always 0.0
Hard Coded Value		Always 0
Quantity		From File
Sales Person		Not Used
Ship To		From File
Ship By Date	Date(MM/DD/YYYY) + Time Hardcoded (12:00:00 AM)	From File + Time 12 AM	Currently this field is not mapped in IDOC, this should be mapped to segment E1J3P03 with qualifier 006.
Material	10 Leading Zeroes + Material	From MEAN Table based on UPC Number
Size		From MEAN Table based on UPC Number
Cancel date	Date(MM/DD/YYYY) + Time Hardcoded (12:00:00 AM)	From File + Time 12 AM	Currently this field is not mapped in IDOC, this should be mapped to segment E1J3P03 with qualifier 006.

• ROC file format with Contract Number

Field Name	Format	Mapping	Comments
Header Record	There is no Fixed length, fields are separated by '~' and data type character
Record Indicator		H
Internet Order Number		Not Used	This is generated in ROC System
Sales Organization		Always 3200
Distribution Channel		Always 10
Division		Always 00
Cust Id(Sold To)		From File
Customer PO Number		From File
Ship To		From File
Sales Person		Not Used
Order Date	Date(MM/DD/YYYY) + Time Hardcoded (12:00:00 AM)	Current Date + Time 12 AM
Ship By Date	Date(MM/DD/YYYY) + Time Hardcoded (12:00:00 AM)	From File + Time 12 AM
Cancel date	Date(MM/DD/YYYY) + Time Hardcoded (12:00:00 AM)	From File + Time 12 AM
Payment Terms		Not Used( Not Necessary, System will determine the Payment Term)
Carrier Service		Not Used
Blank Field		Blank
Customer Group		Not Used ( Not Necessary, System will determine automatically)
Terms Override		Not Used
Dealer Override		Not Used
Contact Persons Phone		Not Used
Contact Persons Fax		Not Used
Contact Persons Email		Not Used
Hard Coded Value		Using Null	GLPR or DOMA OR NULL
Delivery Block		Blank or ZJ when Sales order is already created for Sold to and Customer PO	New Field . This should be mapped to segment E1EDK01-LIFSK
Item Record
Record Indicator		L
Internet Order Number		Not Used	This is generated in ROC System
Cust Id(Sold To)		From File
Customer PO Number		From File
Seq No		Not Used	Some sequence number generated in ROC System
UPC Id		From File
Hard Coded Value		Always 0.0
Hard Coded Value		Always 0
Quantity		From File
Sales Person		Not Used
Ship To		From File
Ship By Date	Date(MM/DD/YYYY) + Time Hardcoded (12:00:00 AM)	From File + Time 12 AM	Currently this field is not mapped in IDOC, this should be mapped to segment E1J3P03 with qualifier 003 .
Material	10 Leading Zeroes + Material	From MEAN Table based on UPC Number
Size		From MEAN Table based on UPC Number
Cancel date	Date(MM/DD/YYYY) + Time Hardcoded (12:00:00 AM)	From File + Time 12 AM	Currently this field is not mapped in IDOC, this should be mapped to segment E1J3P03 with qualifier 006.
Rejection Reason		Blank or ZJ when there are multiple Contracts available	New Field. This field should mapped to segment E1J3P01-ABGRU
Contract Number		Contract Document Number with Leading Zeros or Blank when there is no contract	New Field. This field should be mapped to segment E1EDP02-BELNR with qualifier '043'
Contract Item Number		Contract Item Number with leading zeros or blank when there is no contract Number	New Field. This field should be mapped to segment E1EDP02-ZEILE

• ZJEDI Input File

Field Name	Format	Comments
Header Record	There is no Fixed length, fields are separated by ',' and data type character
Sold To
Ship To
Customer PO
Requested Deliver Date	User Format ( For eg. US Users MM/DD/YYYY and Japan users yyyymmdd etc
Cancel Date	User Format ( For eg. US Users MM/DD/YYYY and Japan users yyyymmdd etc
Jan Id or UPC Number
Quantity

Data Validation

• Duplicate Order (if sold-to+Shipto+PO+ Requested delivery date already processed).
  • Create order but put on delivery hold

• No blank fields
• Any validation errors will result in entire order (SP+SH+PO) being held for correction and reprocessing

Program Output
A log will be created showing

• Program Run date/time, options selected to run program (e.g. source data)
• Successful Orders
• Errors that prevented orders from being loaded
  • Input file Line #,Ship-To, PO number ,Mat, Grid, reason for error

Error Handling
Any order failing pre-load validation checks or BAPI failure will need to be corrected and reprocessed.
Errored orders will be held into an custom table for viewing data. Users will edit the data directly in the input file and reprocess.

• Zerror Table format
  • File name (key)
  • Row Num (key)
  • Date processed
  • Columns: all columns in source file
  • Error reason

Audit report (Z_SO_LOAD_AUDIT)

Tcode: ZJCALL (Audit Reports)

This report is used to assist the testing process. It shows each order in SAP in same format at input file.

• Includes all columns in input file +reject code column

Issues

---

[List Issues / Bugs identified in configuration or development]

1. In scenario with PO# JP-000014, the call off is created with 10 quantity only and remaining 5 is not logged in the error. This is specific to materials with Z2 availability check.

Open Questions

1. Does the season logic need to apply for Japan call offs too

• post orders with rejection when there’s no valid season
• push out dates if cancel/RDD or both are in the past
• post orders with rejection if customer specific season is invalid

2. Assuming answer to the above Question is NO; the IDOCs with errors will fail.

2. Copy contract document date (AUDAT) to the call offs when created with reference.

3. Today calls offs are created via EDI using PO# as reference - How should this be handled assuming there are duplicate PO# (may not belong to same SP)

• look for the contract (with same SP as in the order) and with the earliest RDD in case of multiple as today
• Ignore the load file and log the error for customer service to decide

4. If call off quantity is more than the open reference quantity, the contract will be over consumed (BI reporting impact) though the excess quantity will be from free inventory.

5. If inventory from a given contract is consumed can call offs reference a future contract.