Skip to Content

LSMW issues for Sch. Ageement (Transaction VA31)

Hi ALL,

I am trying for the first time to create a LSMW to upload the Scheduling agreement. Could you pl guide me as to how exactly we map the Ship-to-party and Sold-to-party in BVBPAKOM structure?

I know that we will need to use Partner Type Field i.e. PARVW , if so how can we have one field mapped to two different values i.e. SP and WE at header level?

Also did you do this in one step using this program RVINVB10? How did you manage multiple lines on the scheduling agreement ?

One more problem that I am encountering is that its giving a message Shipping condition '01' is not defined.

The file contains the Shipping condition as '01', however the transaction maintains the Shipping condition as 'STANDARD' against the value of '01'. How to solve them ??

Any input is greatly appreciated.

BR

Tanmoy

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

5 Answers

  • Posted on Nov 21, 2011 at 05:06 AM

    Hi Tanmoy,

    At partner level maintain file.

    Regards,

    Madhu.

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Nov 22, 2011 at 07:31 AM

    What about the error in the Shipping condition ?? Can we use some kind of conversion exits ??

    BR

    Tanmoy

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Nov 22, 2011 at 08:24 AM

    Not yet...I am trying to solve it myself...If I fail then I will take the help of the functional team.

    BR,

    Tanmoy

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Nov 22, 2011 at 09:33 AM

    Hi,

    Regarding the error: Period indicator S is not defined. I have discussed with the functional team without success. However in the debugger I note that the error is getting generated at the execution of this Function Module.

    ...
    CALL FUNCTION 'PERIOD_AND_DATE_CONVERT_OUTPUT'
       EXPORTING
         INTERNAL_DATE   = FVBAKKOM-VDATU
         INTERNAL_PERIOD = FVBAKKOM-VPRGR
       IMPORTING
         EXTERNAL_DATE   = DA_KETDAT
         EXTERNAL_PERIOD = DA_KPRGBZ.
    

    Here the value for:

    FVBAKKOM-VDATU is in the YYYYMMDD internal format

    FVBAKKOM-VPRGR is S, however the internal_period is of type TPRG-PRGRS which has fixed values of:

    1 Day

    2 Week

    3 Month

    4 Posting period

    5 Planning calendar period

    BR

    Tanmoy

    Add a comment
    10|10000 characters needed characters exceeded

    • in customizing transaction O02K you define period indicator.

      you select an internal period indicator, then click the folder for texts for period indicator.

      There you define per language which external indicator is used.

      in my system S = Semaine which is week in french language.

      It depends now in what language you are loading the agreements.

      This S must be somewhere, probably in your source file, or maybe as a constant value in your field mapping.

      But SAP is teling you that period indicator S is not defined, this means SAP has found a S, but cannot use it because it is not a valid character for the language.

      This was just an example, I am not certain if SAP is looking up this table for schedule agreements too, I cant look into the system as we do not use schedule agreements.

  • Posted on Dec 15, 2011 at 10:54 AM

    Please refer to the thread for solution:

    [Self-Solution|LSMW Upload for Scheduling Agreement using RVINVB10;

    BR,

    Tanmoy

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.