Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

LSMW using BAPI to create Schedule Agreements

marcoantonio_romerosanche
Active Participant
0 Likes
596

Hello.

Im using the LSMW with the BAPI option to create schedule agreements. as follow:

BUS2013 Purch.scheduling agreement

CREATE Create

PURSAG_CREATE Create a Scheduling Agree

PURSAG_CREATE01 Create a Scheduling Agree

I already activate the "IDOC inbound Processing" from the Setting main LSMW menu.

File port LSMW

tRFC port

Partn.Type US

Partner No. LSMW

Into LSMW the functions:

Maintain Object Attributes OK

Maintain Source Structures OK

Maintain Source Fields OK

Maintain Structure Relations FAIL

Here Im getting this error: No target structures could be found

Message no. /SAPDMC/LSMW_OBJ_030001

What I can do with that?? Im running over SAP ECC 6.0

Hello.

Im using the LSMW with the BAPI option to create schedule agreements. as follow:

BUS2013 Purch.scheduling agreement

CREATE Create

PURSAG_CREATE Create a Scheduling Agree

PURSAG_CREATE01 Create a Scheduling Agree

I already activate the "IDOC inbound Processing" from the Setting main LSMW menu.

File port LSMW

tRFC port

Partn.Type US

Partner No. LSMW

Into LSMW the functions:

Maintain Object Attributes OK

Maintain Source Structures OK

Maintain Source Fields OK

Maintain Structure Relations FAIL

Here Im getting this error: No target structures could be found

Message no. /SAPDMC/LSMW_OBJ_030001

What I can do with that?? Im running over SAP ECC 6.0

2 REPLIES 2
Read only

marcoantonio_romerosanche
Active Participant
0 Likes
550

We review another system and see that there exist the PURSAG_CREATE01 in WE30, so we are going to copy that structure to the new system.

After that I was able to continue.

Read only

Former Member
0 Likes
550

Hi,

Take a look in this:

/message/5458579#5458579 [original link is broken]

Best regards,

Leandro Mengue