SD-FI - Surya - Deepak - Siba - Raghav - 2016-01-18 - 24193 - Service Request - 2016 Order Fulfillment and HR - Week ending April 22 (Jeffrey Mau by 2016-12-31) #SDSupportOrderEntry
2016-01-18 - 24193 - Service Request - 2016 Order Fulfillment and HR
Problem Summary
All supporting activities that are less than 4 hours in 2016 are updated in this sheet.
Admin Info
| Purpose |
All supporting activities that are less than 4 hours in 2016 are updated in this sheet. |
| Requested by |
Jeffrey Mau |
| Issue Date |
04/18/2016 - 04/22/2016 |
| Resolved by |
Surya/Deepak/Siba/Raghav |
| Resolved Date |
04/23/2014 |
| Document Status |
Resolved |
Detailed Problem Description
(Include Screen Shots if required )01. 04/19/2016 - NEP- User got error message, while packing the delivery # 0083220610 with new packing program. (By Dan)
Error screen shot provided by Dan:
02. Add new fields (customer name, delivery priority) to the report (Analyze sales order change log for AFS rescheduling) executed with transaction /n/AFS/V_R2.
03. Duplicate sales orders were created on 4/18 for EMEA.
04. 04/23/2016 - Research on the customer ID FI posting flow to COPA
05. Test SAP proposed notes - 2110780 and 2265046 to fix an issue caused during contract-call off creations via IDOCs
Solution Analysis and Recommendations
(Include Screen Shots if required)01. 04/19/2016 - After debugging of packing program it is found that, while packing the delivery # 83220610 program is checking the table entry against the Silhouette and found no entry for the specific silhouette. So the error message is coming out.
Below is the screen shot of table entry - ZPWEAVER_SHMAS from NEP:
The same entry is missing in NEQ600 also. So for confirmation, we created a test data in NEQ600 with PH4- 388 and packed the delivery document. We found the same error message as output.
Example:
SO # 2768973
DELIVERY # 82942796
Screen shot from NEQ600 after packing the above delivery document:
2. Standard enhancement spots are not available in the report. The report has to be cloned and code written to output the two fields. A high level effort of 40hrs would be required to accomplish the task.
3. The IDOC generation job CREATE_IDOCS_WEB_UK for EMEA encountered bad data in the load file which resulted in the file not archiving. This caused the file to be processed multiple times until it was realized that duplicated orders were being created.
Options –
A. Reduce the frequency of the job schedule. The last one month (03/01 to 04/19) job details show that the job finishes successfully at these times –
01:20, 07:20 and 13:20. Do we really need to have it as frequently as 10mins?
By doing so, we can not only overcome such issues but also gives us time for identifying it.
B. We could have a manual check for bad data before the job processes. I’m not sure if there’s a process to check the files before loading to the directory. I don’t think we have seen such issues recently?
Technically it is highly difficult to propose a solution since the file name is always the same. I think we have discussed this in the past – having different file names but we chose otherwise?
04. Analysed and sent requirements to NE
05. Reproduced the two scenarios as outlined in the notes - contract is over consumed by call offs when created via IDOCs. The tests should be run again once the notes are implemented in DEV.
Resolution
01. 04/19/2016 - We suggested, to maintain the corresponding BoxSize for PH4- 388 and try packing the delivery document and try packing the delivery # 83220610 afterwards.
Release Information
Provide link here to Release Notes if Technical Objects were changed