hemanth
Member
JD Edwards EnterpriseOne 9.1
Tools Release 9.1.5
SOA executing standard JP430000 to create Purchase Order for which customer has the business need to track and save Environment values such as (source & destination) details, coming from the 3rd party.Upon initial add the Environment details to be populated. However, after executing JP430000 to update the Environment details (source & destination) is not updating in WSDL file as (XML schema).
EXPECTED BEHAVIOR
-----------------------
When executing standard JP430000 BSSV it should update in WSDL (XML Schema). It should not be blank
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Execute JP430000 via SOAOPUI to include user date:
2. Check F4301/customise table to see if JOBN gets populated.
3. Execute JP430000 via SOAOPUI to change user date.
4. Check F4301/customise table and data is not updated.
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot implement this integration.
Tools Release 9.1.5
SOA executing standard JP430000 to create Purchase Order for which customer has the business need to track and save Environment values such as (source & destination) details, coming from the 3rd party.Upon initial add the Environment details to be populated. However, after executing JP430000 to update the Environment details (source & destination) is not updating in WSDL file as (XML schema).
EXPECTED BEHAVIOR
-----------------------
When executing standard JP430000 BSSV it should update in WSDL (XML Schema). It should not be blank
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Execute JP430000 via SOAOPUI to include user date:
2. Check F4301/customise table to see if JOBN gets populated.
3. Execute JP430000 via SOAOPUI to change user date.
4. Check F4301/customise table and data is not updated.
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot implement this integration.
