cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Assign IM mouvement to WM - Check table T156SY: entry XXX does not exist

sonnyBarros
Explorer
0 Kudos
1,425

Hello everyone,
For context:
I'm working on an ECC6 environment.
I'm trying to create a WM movement and then link it to a MM movement.
This movement will be called with the BAPI_GOODSMVT_CREATE.
So I've created the movement in SPRO. I then linked the movement through the SM30 on view V_156SC_VC as I needed to add a line and couldn't find any other solution.

My problem:
When calling the BAPI, the following error comes up “Check table T156SY: entry 311 X X Q B _ P does not exist” and indeed the table row doesn't exist and I can't find a way to fill it. Either via SPRO or SM30.

sonnyBarros_0-1718116022738.png

Do you know how to do this?

Thanks in advance

View Entire Topic
RaymondGiuseppi
Active Contributor

Did you try SM30 on view V_T156SY (or a small abap report) 

  • mainenance views V_156SC_VC, V_T156SY and V_156X_VC can be relevant to your requirement,
    BUT
  • ⚠️ NB: this is a 'system table, edited only by SAP, change = modification' ⚠️ So basically you shouldn't perform modifications that require to change this table
sonnyBarros
Explorer
0 Kudos
Hello, thank you for your prompt reply. No, I hadn't tried it because I wasn't familiar with this solution. When I try it I get the following message: "Do not make any changes (SAP data)" and "Changes to repository or cross-client customizing are not permitted" Is it because I lack rights? Thank you
RaymondGiuseppi
Active Contributor
  • The first message corresponds the delivery class of the table, it is 'S' so only SAP is allowed to maintain
  • The second messages caused by the fact that the table doesn't handle client MANDT as a key (so not allowed by default)

You could change the table delivery class with SE11 from S to G and open change with SCC4 to remove second message (good luck at next upgrade and side effects)

But you shouldn't, better try to raise an incident/case to OSS or change your solution.

sonnyBarros
Explorer
I think it's wiser to try another solution. I'm going to modify my BAPI parameters to work on a row that already exists in the table.
Ask a Question