This section details possible VCP Base Pack Integration failure points.
This appendix covers the following topics:
After the UBE extracts are complete, use Submitted Jobs to check the .pdf log for errors. UBE extracts must be rerun after the reported error has been resolved.
Collection and publish concurrent programs stop running when an error occurs. An error message indicating the failed component is logged to the concurrent program log file. The concurrent program must be relaunched after the reported error has been resolved.
Collection and publish concurrent programs stop running when an error occurs. An ODI error log file is generated. This file contains the session number of the failed ODI session and the cause of the error.
Important: Ensure that all directories to which files are being written into are not write protected.
The following downstream concurrent programs may cause errors:
Legacy ASCP collection programs (pre-processor and ODS load)
Legacy Demantra collections program for Sales History
Demantra collection programs for Calendar, Price List and UOM
Collection and publish concurrent programs stop running when an error occurs. An error message indicating the request ID is logged to the concurrent program log file. Search for the failed request in the View Requests form.
Errors could be caused by any of the Demantra workflows. Collection and publish concurrent programs stop running when an error occurs. An error message indicating the workflow execution ID is logged to the concurrent program log file. Search for the failed workflow in the View Requests form.
After deploying ODI web service for GOP, the GOP_WS_DEPLOYMENT.txt log file is created inside the /tmp folder.
If the MSC: ATP Debug Mode profile is set to Yes, GOP session files (debug files) are located at $DOMAIN_HOME/servers/AdminServer/logs/ with the name session-{sessionId}. If DOMAIN_HOME is not defined, the session files are created in the /tmp folder.
For example, if the following has been set:
DOMAIN_HOME= /slot/ems4413/oracle/Middleware/user_projects/ domains/soa_domain/
the session files are placed under DOMAIN_HOME/servers/AdminServer/logs
or
/slot/ems4413/oracle/Middleware/user_projects/domains/soa_domain/servers/AdminServer/logs
To ensure that the application is working correctly, you can test it by sending a sample payload.
To test the GOP web service:
In the WLS Administration Console, navigate to Deployments.
1. Click msc_ws_atp_ws.
2. Click the Testing tab.
3. Click the OrderPromisingService tree item.
4. Click Test Client.
5. Copy and paste the following sample payload in the Test Client URL
<target:promiseSalesOrders xmlns:target="http://oracle.apps.msc.atp.service/">
<username>mfg</username>
<respname>Advanced Supply Chain Planner</respname>
<respapplname>MSC</respapplname>
<securitygroupname>STANDARD</securitygroupname>
<language>AMERICAN</language>
<atpInputs xmlns:orac="http://oracle.apps.msc.atp.service/" xmlns:soap11-enc=http://schemas.xmlsoap.org/soap/encoding/ xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance soap11- enc:arrayType="orac:ATPInput[]" xsi:type="orac:ArrayOfATPInput">
<item xsi:type="orac:ATPInput">
<action>100</action>
<customerCode> </customerCode>
<identifier></identifier>
<inventoryitemname></inventoryitemname>
<quantityordered></quantityordered>
<quantityuom> </quantityuom>
<requestedshipdate>2011-10-30T05:30:00</requestedshipdate>
<sourceorganizationcode> /sourceorganizationcode>
</item>
</atpInputs>
</target:promiseSalesOrders>