Need to see data in PO that isn't posted yet due to error in PO processing.

[former_member277592]

I'm asked to correct an error in an IDoc related to the PO in transaction wlf_idoc.

The PO isn't posted yet due to the error in the Idoc.

Transactions like me2n, se16n table ekko/ekpo and me23n don't work as the PO isn't prosted yet.

In order to correct the PO correctly for one article that has been bought in by a shop, i need to view the purchase price data of the item in that unposted PO.

So a bit a vicious cycle -> PO not posted yet due to error, but need some info in the PO to correct that error.

Can i use a se16n table or specific transaction to access the data in the erroneous PO?

Just for additional information:

Two numbers are currently used for articles in the PO, old and new (new being an article in SAP), as a transition from an old database system is being done.

If the link between the old and new article isn't made this results in the PO going in error before posting. It will give the old Nr. and i have to find the new article nr. to correct the PO Idoc based on information i can find with the old Nr. / purchase price etc.

The orders by the shops based on old article Nr.s so in some cases it's even possible the corresponding SAP article with new Nr. doesn't exist yet.

[former_member277592]

Txs for the suggestions, I'll try that table edid4 out when i have access to SAP next week and see if i get any further.

as for the BD87 code, i've used it to process corrected Idocs that aren't processed by the system yet but haven't seen it used for investigating IDoc content with it yet.

wlf_idoc don't give the info needed when opening the idoc. It gives date, article name, order amount, order unit. But not the pruchase price of the item which is in the PO data tables somewhere.

[leonardofreitas]

Hi,

T-code BD87 may be also good to select records to be displayed and analysed!

Thanks

Leonardo de Freitas

[JL23]

Try your luck with SE16N at table EDID4, this is the table that has all IDOCs, the content is in field SDATA

You will pretty quick realize that this is not going to work well for you.

You have not yet a PO, you just a long data string (SDATA field) and meta information that enables existing programs to create a PO from that data.

Looking into the IDoc via WE02, WE05 or even BD87 (sorry BD84 was a typo) or from WLF_IDOC is more efficient than SE16N.