E1: OUTBND: RTPOOUT RTPOOUT2 - Purchase Order RTE Known Issues and Other Information
(Doc ID 1618655.1)
Last updated on APRIL 17, 2023
Applies to:
JD Edwards EnterpriseOne Tools - Version 8.98 to 9.1 [Release 8.98 to 9.1]Information in this document applies to any platform.
Purpose
This Document is intended to provide details of known issues and other information about the Purchase Order Real Time Event RTPOOUT (and any available versions of RTPOOUT)
Troubleshooting Steps
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Purpose |
| Troubleshooting Steps |
| Defects |
| Scenario: RTPOOUT is not Populating the MnPlanningQuantity (UOPN) |
| Scenario: RTPOOUT Does not Contain the Following Fields RKCO, RORN, RCTO and RLLN |
| Scenario: RTPOOUT Wrong Status is Generated when Approved Order is Modified (approval) |
| Scenario: RTPOOUT status 280 is not Generated when Purchase Order is auto Approved |
| Scenario: RTPOOUT Event Fires Even When Suppliers Correspondence Method (F0401.CRMD) Is Not Set To 5 |
| Scenario: RTPOOUT Realtime Event is not Triggered when PO is created with Approvals switched on when using JP430000 |
| Scenario: RTPOOUT only working when both RTPOOUT and RTPOOUT2 are activated |
| Scenario: Extra RTE RTPOOUT2 generated with cancelled lines |
| Scenario: Extra RTE RTPOOUT/RTPOOUT2 generated when adding a new line to an existing order AND using PO Approval auto approve |
| Scenario: Extra RTE RTPOOUT2 generated with cancelled lines |
| Enhancements |
| Scenario: RTPOOUT Not All Data Items From F4301 and F4311 Are Included In The XML Output |
| Scenario: RTEPOOUT And PO Header Updates to Order Address Do Not Generate RTPOOUT |
| Other Issues |
| References |