LSMW issues for Sch. Ageement (Transaction VA31)

[Former Member]

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

[madhu_vadlamani]

Hi Tanmoy,

At partner level maintain file.

Regards,

Madhu.

[Former Member]

Can you please clarify the point stated. Do you want me to maintain a separate file at the partner level:

 Structure: BVBPAKOM ??

BR

Tanmoy

Edited by: Tanmoy Mondal on Nov 21, 2011 9:39 AM

[madhu_vadlamani]

Hi Tanmoy,

Yes maintain a separate a file the same.

Regards,

Madhu.

[Former Member]

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

BR

Tanmoy

[Former Member]

Its solved with a leading zero missing. However I am now getting a new error: Period indicator S is not defined. The Function Module:

... SD_SALES_HEADER_MAINTAIN  

returns the following error: Period indicator S is not defined.

BR

Tanmoy

[madhu_vadlamani]

HI,

Did you shown this to functional people.

Regards,

Madhu.

[Former Member]

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

BR,

Tanmoy

[Former Member]

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

[JL23]

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.

[Former Member]

Please refer to the thread for solution:

[Self-Solution|;

BR,

Tanmoy