Skip to Content

One of the more common problems occurs after data had been copied from the productive system to a test or development system, there on the target system the accounting document is not shown in the document flow of the invoice:

Accounting.gif

The accounting document exists in reality, but when clicking on the accounting button in transaction VF03, then the error message occurs, that it had not yet been created (error message identification VF062):

Acc_missing.gif

The root cause is the logical system, which is for the created invoice (table field VBRK-LOGSYS) not identical to the one to which the client is assigned (table field T000-LOGSYS):

VBRK_T00.gif

The solution in this case is to convert the logical system in VBRK to the one used in the client.

There is a standard tool for this conversion, the transaction BDLS:

BDLS.gif

Here the old logical system name and the new one (to which the client is assigned) will have to be inserted, and for table VBRK a conversion of the table triggered. First in a test run it can be checked what would the system do:

test run.gif

The number of relevant entries should correspond with the number of invoices that have the old logical system in table VBRK, which can be verified by selecting in transaction SE16:

/wp-content/uploads/2014/10/number_555166.gif

One known issue that can prevent the conversion is in case the protocol tables :

BDLSHDR

BDLSPOS

BDLSLOG

do still have entries. This can also be seen in SE16 by inserting the table names and checking the number of entries as shown above.

In case data records are present in any one of them, then the report RBDLSMAP_RESET will have to be executed before using transaction BDLS. If this report is not yet present in the system, it can be implemented from note 962674.

To report this post you need to login first.

8 Comments

You must be Logged on to comment or reply to a post.

  1. Pradeep Mani

    Nice documents from your end,

    I request you to help me on this.

    We do intercompany stock transfer.

    Our client requirement is as below,

    During MIGO in receiving plant the accouting enrty

    Inventory G/l 1 Dr (BSX)

    GR/IR Cr

    While selling the material to end customer in

    receiving plant ,we do PGI.

    They need accouting entry as below,

    COGS Dr

    Inventory G/l 2 Cr (BSX)

    We tried to work out but it is hitting same Inventory G/L(i.e We cannot differentiate Inventory G/L during MIGO & PGI)  ,but it is not possible by us.

    Is there any standard procedure to do this.

    Else also provide us is there any user exit available,so that modification can be done to hit different Inventory G/L accounts.

    Thanks,

    Pradeep M

    (0) 
      1. venu gopal

        Dear Tobaias ….Thanks a lot for your post sharing

        one small Doubt please let me know

        Here i have not understand Productive system to Test system or logicel system

        i mean P—D Or P–Q

        Please explain a bit confused

        Thanks a lot

        (0) 
        1. Tobias Reiner Dolgener Post author

          Hi venu gopal,

          in the first sentence I explained in which situtation this problem occurs.

          After you have copied from productive system to a test system, the logical system in the invoices (field VBRK-LOGSYS) will have to be adjusted to the one used in the target system (field T000-LOGSYS) in case those are not the same.

          Otherwise the accounting document can not be shown in the document flow.

          Best regards,

          Tobias

          (0) 
  2. Szabolcs Dombo

    Hello Tobias,

    long time no speak! Thanks for this brief documentation, if was indeed very useful. This is the answer I was looking for!

    Regards,

    Szabolcs

    (0) 
  3. Eric Brokk

    Great information! Thank you for this. By the way, we are going to post our new article with like issue. It contains info about Accounting document not shown in VF03 document flow after client copy. And your article will be so useful for us. Can we, please, use your information to conclude our post on http://originformstudio.com/. Thank you for reply!

    (0) 

Leave a Reply