Request Fulfillment Report – Actual End Date incorrect
[/APC/SCMRF_C3] [BYD] [FP2.0] [fulfillment] [fulfillment agent] [incorrect] [login incorrect]
Related:
- BP DX:Outbound incorrect when ADRU entries are missingSymptom During dataexchange of Business Partners, if the communication data...
- SAP BP:Text of Error Message R1 477 and R11 186 is incorrectSymptom Text of Error Message R1 477 is incorrect. Other...
- Incorrect duplicate check occurs on changing BP nameSymptom When the business partner name is changed using Web...
- Validity of address independent communication data incorrectSymptom Validity of address independent communication data is inconsistent after...
- BYD_HF:Posting date is incorrect in generated DE MT940Symptom After upload of the DE MT940 bank statement file...
Symptom
In the Report ‘Request Fulfillment Report’ in the Work Centers Production Control and Supply Chain Control, the Actual End Date and On Time Status are not showing the correct value in some cases.
Other terms
BYD, FP2.0, /APC/SCMRF_C3
Reason and Prerequisites
If there are more than one Lot per Production Request Segment, the maximum of the End Dates of all Production Lots has to be calculated per Segment. The old implementation of the end routine of the InfoCube /APC/SCMRF_C3 is not calculating the maximum of dates correctly.
Solution
The following manual steps are relevant only for systems which are already set up and running on FP2.0 SP0:
Manual post-processing required:
Target group : BI
Target systems : All run-time systems where BI is activated
Effort and runtime : 20 minutes
Execution : uptime
Required for new installation : No
After the import of hotfix H0EK003072 to ByD FP2.0 SP0 system, the following manual steps have to be done:
1. Go to tx /nRSOR to check that the correct source systems (myself and A1S Web Service) are selected.
2. Go to tx /nSE38, enter report name RSO_CONT_ACT_FOR_REQUESTS and execute.
3. Option for ‘Transport Request’ shall be checked as ‘MANUAL’.
4. Enter the request H0EK003072 and schedule the program. Please execute the report in background (Menu->Programm->Execute in the Background).
5. Check the job with job name RSO_CONT_ACT_FOR_REQUESTS in tx /nSM37.
6. If the job is cancelled, analyse the job log and try to solve the basis of job failure. If it’s not possible to solve the problem by your own, please create ticket for the responsible application and component.
Otherwise reset the status of the conversion object 2SP00_/APC/SCM_TD_SCMHP01_NR and reschedule as described in 2.-4. Reset the status via tx /nSE16 for table RSOBIXPSTATUS for BIXP_ID = 2SP00_/APC/SCM_TD_SCMHP01_NR, the value of STATUS value has to be set to blank or ‘E’.
7. After the job is finished, go to tx /nSE38 execute report RSO_CONT_ACT_FOR_REQUESTS to check the log. Use the button ‘Display Logs’ to select the logs. Analyze the logs: Only yellow and green messages should occur.
8. Please check also with tx /nRSPCM that process chain /APC/SCM_TD_SCMHP01_NR is running successfully.
In case of red messages, open a message on component ‘SRD-SCM-ANA’.