How to implement R47011 to create Customer’s PO (that is, Sales Order of your company)
A. Create flat file to convert Text file into SQL format via R47002C
a. 1-Header File
b. 2-Detail File
(Convert below potion into Text fle)
"1","JDE ","5 "," ","1000"," ","ORDERS "," ","0","1","1"," "," ","02","12000","1771","OP","000"," 12061","12000"," "," "," "," "," ","10768","10071","0","0","0","0","0","0","0","0","0","S090605 "," "," "," "," "," "," "," "," "," "," "," "," "," "," ","0"," "," "," "," ","0","0"," "," "," "," ","Y","Y","0","0"," "," "," "," "," ","1"," "," ","N"," "," "," "," ","0","F"," ","0"," ","0"," "," "," ","0","0","0"," ","JDE ","JDE ","P4311Z1 ","SGRCNSH004","105175","170215"
"2","JDE ","5 "," ","1000"," ","ORDERS "," ","0","1","1"," "," ","02","12000","1771","OP"," ","1000"," 12061"," "," "," "," ","0"," "," "," ","0"," ","0","N","10768","10071","0","0","0","0","0","0","0","0","0","0","0","0","S090605 "," ","1290","SUGB103 ","7610522265462 "," "," "," "," ","0","0"," "," ","S "," ","220"," "," "," "," "," "," "," "," "," "," "," ","EA","1","0","0","0","0","0"," ","200000","0","0","0","0","0","0","0"," ","0","0"," "," "," "," "," "," "," ","0"," "," "," "," "," "," "," "," "," "," "," "," ","F","0","0"," "," "," "," "," ","0"," ","0"," ","0"," ","0"," "," ","20","0","S "," ","Y","Y","0"," ","AA"," "," "," "," "," "," "," "," ","0"," "," "," "," "," "," "," "," ","1"," "," "," "," "," "," "," "," "," "," "," "," "," "," "," "," "," "," "," ","0","OP","0","0"," ","0","0","0","0","0","0","0","0"," ","0","0","0"," "," ","JDE ","R4311Z1I ","SGRCNSH004","105178","103113"
à For further detail, you may refer table layout of F47011/F47012
à In case you have 1:m relationship between header and detail files, the file should be formated as follows,
Example:
1SO01
2SO01 1.000
2SO01 2.000
2SO01 3.000
2SO01 4.000
2SO01 5.000
1SO02
2SO02 1.000
2SO02 2.000
2SO02 3.000
: As you observe above, DOCO should be determined upon writing F47011/F47012.
In case you save data into FTP Server (or different machine which function as a server)
- Windows: \\ServerName\FolderName\FlatFile.txt (or without *.txt as this is general format of Flat file)
- Unix: \servername\foldername\flatfile (make it sure, it’s case sensitive)
B. Based on above information define P47002 properly
a. To create Sales Order or to run R47011, table F47011/F47012 is sufficient
b. Table F47013/F4706/F4714/F4715 are optional tables
c. For further information, ask client to refer JDE Help Document
à Above information tells us Processing Option parameter
As you can refer above, “Receiving customer orders (850/ORDERS)
Make it sure; this application is to convert Customer’s Purchase Order into client’s Sales Order. All the function, which is supported by P4210, should be supported from this application.
C. In case you donot convert F47013/F4706/F4714/F4715, delete those settings from here. Make it sure, system will refer
a. Flat File Name
b. Record Type “1” and “2”
c. Table Name F47011/F47012
à Flat file was defined as above
à In case they want to create F47013, they need another file which and set the first column data “5”
D. To create/insert information into F47011/F47012, run R47002C
à If you want to run R47011 with conversion, you may specify “Conversion Application R47011” and valid version
à R47002C will convert Flat File format data into SQL format data. However there is no Data Validation
Now the actual data from F47011/F47012 is defined as follows (mandatory columns and optional columns),
- In case you can validate as much columns as possible, the performance of R47011 will be faster
- EDOC value will be get from NN (47|02)
- EDBT value will be get from NN (47|01)
- However above setting is not mandatory
Now some other mandatory columns:
- EKCO: EDI Company
- EDOC: The value from NN (47|02) conventionally
- EDCT: Sales Order Type (if necessary, you may define new EDI S/O Type)
- EDLN: EDI Line Number
- EDST: ORDERS (Default)
- EDER=’1’ (Default)
In case you write DOCO, DCTO, KCOO, LNID actual sales order will be follow the value assigned from F47011/F47012
Now, above information is technical setting
Usually, the information need to be provided further is,
- AN8
- SHAN
- LITM
- UOM
- UORG
- TRDJ
- DRQJ
- VR01 (Customer’s PO)
- CRCD
- UPRC
- AEXP (In case there can be round up issue)
In case it’s necessary for you to create flat file for client, you may enter above information via P47011 and convert it to flat file
WORKAROUD:
A. Case Study 1
: Customer’s PO (Flat File) Received by FTP
Considerations: In case you received the file as shown above, you don’t have to take conversion process, but in actual world, your customer won’t listen to you. Then the flat file format won’t be same with suggest format above.
Best practice seems likely that,
- Fixed width
- No deliminator
· Header
· Body
· Trailer
a. Header info (fixed length)
- Identifier (START, 1 Code etc.)
- File Name
- AuditDate
- AuditTime
- The length of each rows
b. Traier info (fixed length)
- Identifier (END, 3 Code etc.)
- File Name
- AuditDate
- AuditTime
- Total number of lines
c. Body
- Identifier (M-main, 2 etc.)
- PO Number
- Order Date
- Order Time
- Other reference
- Request Date
- Deliver Date
- Bill To Code
- Ship To Code
- Delivery Code
- Part Number
- Unit of Measure
- Quantity
- Unit Price quoted
- Currency Code
- Order by
- Other reference
-
· Define
n Data format (YYYYMMDD)
n Amount Format: 999999999.9999 etc
n Synchronize the code between your customer and your organization
-
In this case, you need to write “Conversion application” using JDE Tool set or DBA Tools that will convert flat file format into SQL format file. You may write data into F47011/F47012 directly. Upon running R47011, which will create Sales Order accordingly
B. Case Study 2
: This EDI configuration need clear role definition between your customer and your company. For this reason, the incoming flat file should be validated before you write F47011/F47012
a. Convert flat file into SQL file
b. Validate it
- Good: Insert into F47011/F47012
- Not Good: inform customer to handle flat file again