Vi01 - Issue in conversion of partner function data in VTPA table

[Former Member]

Dear All,

In VI01 tcode while creating shipment cost document, system gives error message as see log.

"Item not created because service agent CR not in reference document".

When debug, it is found that system is not converting data of table VTPA from PARVW (SP) to CR in following FM.

SD_SCD_ITEM_INITIALIZE

at line no. 55

* determine relevant partner
  READ TABLE I_REFOBJ-VBPA INTO L_VBPA_WA
                           WITH KEY POSNR = I_TSNUM
                                    PARVW = I_TVFT-PARVW   BINARY SEARCH.

please help if anyone has idea of this type of error.

Thanks in advance,

Rajesh Vasudeva

[JL23]

In general I would focus on the message "Item not created because service agent CR not in reference document"

Do you have any proof that a CR partner is in the reference document? screen shots from document or table?

You probably know that a partner function key is a German abbreviation SP = Spediteur

And in customizing you actually maintain that SP is e.g. CR for carrier in english

Looking at your document you should then see a partner CR, looking into the table you would  see a SP  if the conversion exit is not active in your SE16, or you see a CR if the conversion is activated.

So far the coding does not tell much.

But the message says that a CR partner is missing.

I would suggest you check your customizing to find the relation from the original key to your CR.

then check the reference documents if you have a partner for this role.

[Former Member]

Hi Jurgen L,

Thanx for reply.

As desired, enclosed please find xml file having screen shots of forwarding agent in reference doc and error message. Please note that error starts after changing Generate PO option (from 'B' to 'A') in t_56 tcode. Before that it was functioning perfectly OK.

regards,

Rajesh

[Former Member]

Pls. reply ASAP.

please treat it as urgent. Annual closing is hampered.

regards,

Rajesh

[JL23]

What if you change T_56 back from A to B, does it then start to work again?This would at least be a proof that this has caused the problem (I actually do not believe that this has any relation

[JL23]

By the way, do not use ASAP. the people here help you voluntarily. They do not get paid to help you. You can urge people if you buy a service, but you cannot urge volunteers, they might just stop helping.

Every post is equally important. If you have a problem which cannot wait, then open a call at SAP Support

[Former Member]

If u don't have solution, please don't teach me to whom I have to open a call. For your information, I have already logged call on SAP & our support partner with high priority, they are working on issue but not able to deliver concrete solution.

By the way I have requested not urged the forum for help, I can't understand the comment made by u that "they do not get paid to help you", where I have said I am paying for getting help? Please don't make such type of comments, it doesn't look nice.

Thanks for helping me, I got the solution by doing changes in configuration other than t_56, now able to create shipment cost documents in quality & production server, will share the solution very soon.

[Former Member]

Please reply, matter is urgent, annual closing is getting stuck.

regards,

Rajesh