Aarto
Reputable Poster
Hi list!
We are facing a project in which the customer wants to use a 3d party Warehouse management system that has to be interfaced to OneWorld.
When it comes to sales order process, we would like to use the F47 files as basis for communications with the WH system. Entered sales order could be populated to F47131/F47132 by using R42500 (batch ship confirm) without calling R47500 (Inbound transaction processor) in the end section. We could then export these files to the local WH system.
The local WH would then process the orderlines and if any picking deviations are reported, we could update F47132 with the actual picked, backordered and cancelled quantities
So.. to test this, I ran the batch ship confirm R42500 UBE followed by R47500 (Modifying the F47132 file before R47500 was ran, changing the shipped/backordered/cancelled qty:s)
Alas, R47500 apparently only processes the lines where F47132 qty:s are identical to F4211 qty:s. If the F47132 qty:S were changed after the R42500 was ran, these lines would be reported as errors.
Only the lines where qty:s were unchanged were processed by R47500
In a previous project we had to write an RPG ship confirmation application from scratch and i would really like to avoid that if at all possible..
Has anyone else faced the same problem? Any tips?
Maybe we have to modify R47500 to accept differences between F47132/F4211 and to treat F47132 as 'manual input' that overrides F4211 data
Grateful for any tips..
OneWorld Xe
AS/400
Regards..
Aarto Reponen
Application Consultant
SYSteam Applications International Consulting AB
Mobile: +46 703 089 284
E-mail: [email protected]
http://www.systeam.se
We are facing a project in which the customer wants to use a 3d party Warehouse management system that has to be interfaced to OneWorld.
When it comes to sales order process, we would like to use the F47 files as basis for communications with the WH system. Entered sales order could be populated to F47131/F47132 by using R42500 (batch ship confirm) without calling R47500 (Inbound transaction processor) in the end section. We could then export these files to the local WH system.
The local WH would then process the orderlines and if any picking deviations are reported, we could update F47132 with the actual picked, backordered and cancelled quantities
So.. to test this, I ran the batch ship confirm R42500 UBE followed by R47500 (Modifying the F47132 file before R47500 was ran, changing the shipped/backordered/cancelled qty:s)
Alas, R47500 apparently only processes the lines where F47132 qty:s are identical to F4211 qty:s. If the F47132 qty:S were changed after the R42500 was ran, these lines would be reported as errors.
Only the lines where qty:s were unchanged were processed by R47500
In a previous project we had to write an RPG ship confirmation application from scratch and i would really like to avoid that if at all possible..
Has anyone else faced the same problem? Any tips?
Maybe we have to modify R47500 to accept differences between F47132/F4211 and to treat F47132 as 'manual input' that overrides F4211 data
Grateful for any tips..
OneWorld Xe
AS/400
Regards..
Aarto Reponen
Application Consultant
SYSteam Applications International Consulting AB
Mobile: +46 703 089 284
E-mail: [email protected]
http://www.systeam.se