Skip to Content
avatar image
Former Member

Subsequent listing in WPUBON idoc processing

HI Experts,

Subsequent listing indicator 2 is set in store site master.

WPUBON inbound idoc is failing as system not performing in subsequent listing.(no entries in WLK1 and MARC).

Is subsequent listing allowed in WPUBON idoc processing?

If yes,what settings/enhancements are missing?

Appreciate your help.



Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Jun 29, 2017 at 05:06 PM


    No it is not allowed as per my knowledge.You need to schedule LIKOND Idoc for the same from inside Exit of WPUBON idoc posting.



    Add comment
    10|10000 characters needed characters exceeded

    • Hi,

      Thanks for the relevant question. I will describe possible scenario and pros &cons of the same solution running on production environment.

      Approach 1 : inside exit of WPUBON IDOC processing you have exit/BADI --> BADI_WPOS_WPUBON. Till this point article in question has not reach failure status,neither the WPUBON idoc finished processing.You need to implement the badi-->prepare IDOC data for LIKOND structure and trigger inbound idoc using FM( IDOC_INBOUND_SINGLE).

      In the partner profile setup (WE20), for WPUBON msg.typ-->you should maintain Trigger by background mode of IDOC posting.(it will ensure 64 status of WPUBON) & for LIKOND msg.typ --> maintain trigger immediately.generally LIKOND rarely fails to post. So it will post immediately creating listing and subsequently The idoc processing job (RBDAPP01) will pick up the WPUBON idoc with 64 status and try to post.At least this time no listing error will come and if all other data and config are ok ,wpubon will be success (53 status).

      Tips:Since inside BADI you can not use Commit work,so we used starting at NEW task for the FM of LIKOND idoc generation. This solution worked fine.

      Cons: If you have huge volume of WPUBON,then there is potential risk of running out of available work process or LUW,since new task generation happens for LIKOND. However,you do expect,most of the articles already listed.

      so before triggering LIKOND you must check WLK1,if it is not listed,then only fire idoc.

      Approach 2 :inside exit of WPUBON IDOC processing you have exit/BADI,where you can submit the PROGRAM of listing ,WSP4 (t-code) get the program name MENU->System. This solution is also tried and tested OK.

      Cons: There is standard SAP program bug/ locking issue for listing process-(WSP4 /WSM3)and it is random/rare. You might face it during concurrent parallel process run.

      Finally these are insurance for the negative failure case and ideally the process could be fine tuned so that all articles are listed beforehand to the respective site- that is ideal and practically rarely complied.

      Hope above explanation is helpful!!!