cancel
Showing results for 
Search instead for 
Did you mean: 

Delivery order by IDOC

Former Member
0 Kudos

Hi Experts,

I'm trying to make a delivery order by IDOC type DELORD (ORDERS05). Does any one process with this type of massage?

I create several orders, but I still have a problem with orders. They look almost the same but still not working.

Could some one write me requirements for this massage? For example links between Idoc segments and fields from Schedule agreements.

Any help will be appreciated.

Edited by: Michal Jesionek on May 31, 2008 4:15 PM

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Michal,

Can you please tell me what exactelly error your are getting, so that we can try to give you some solution.

To check error please go to WE02

Cheers !!!

Imran

Former Member
0 Kudos

The system could not find a scheduling agreement

Message no. VG220

Diagnosis

The system could not find a scheduling agreement with the selection criteria: Customer masterial MATNUM, sold-to party 0000200022, unloading point and customer reference number .

Former Member
0 Kudos

Hi,

Can somebody provide me with the required configuration for incoming IDoc type Delord? I need this massage to create a sales order in reference to scheduling agreements.

Data like Partner Profile, logical system are maintained correctly. We received other Idocs like Delins from this customer.

Please help, it's urgent!

Thanks in advance!

Edited by: Michal Jesionek on Jun 5, 2008 12:31 PM

Former Member
0 Kudos

Anybody ever deal with that IDoc?

Answers (3)

Answers (3)

Former Member
0 Kudos

Hello,

just a simple tip.
I was having the same problem when after all I have figure that the problem was not in the DELORD file but the Scheduling agreement.

I had to process the ORDERS for a TFM type scheduling agreement, but it was created another type that doesn't accept orders.

Former Member
0 Kudos

Michal

Did you find a solution to this problem??

Vendyres

Former Member
0 Kudos

Not really... I extended this issue to OSS and the wrote me couple useful information. Please see below:

Please use transaction WE60 for documentation on the idoc basic type.

Please also see the long text for the error VG220:

.....

Short Text

The system could not find a scheduling agreement

Diagnosis

The system could not find a scheduling agreement with the selection

criteria: Customer material , sold-to party , unloading point and

customer reference number .

.....

Scheduling agreement is based on the following in FM IDOC_INPUT_ORDERS :

o customer material number,

o customer number,

o customer description of partner,

o unload point.

o The checks are made also for rejected scheduling agreement.

In foreground mode :

The system propose to select manually a scheduling agreement from the

the list selected.

In background mode :

It tries to find a document with the above information.

After this advise I'm triggering Delords in foreground (3rd option) in WE19, but it is not the most comfortable way.

If You would find something better please let me know.

Former Member
0 Kudos

HI ,

Please find the info as follows.

E1EDP20 : IDoc schedule lines

Segment definition E2EDP20001 Released since Release 46C , Segment length: 0061

WMENG : Scheduled quantity

internal data type : CHAR

Internal length : 000015 characters

Position in segment : 001, Offset : 0063. external length : 000015

AMENG : Previous scheduled quantity

internal data type : CHAR

Internal length : 000015 characters

Position in segment : 002, Offset : 0078. external length : 000015

EDATU : IDOC: Date

internal data type : CHAR

Internal length : 000008 characters

Position in segment : 003, Offset : 0093. external length : 000008

EZEIT : IDOC: Time

internal data type : CHAR

Internal length : 000006 characters

Position in segment : 004, Offset : 0101. external length : 000006

EDATU_OLD : IDOC: Date

internal data type : CHAR

Internal length : 000008 characters

Position in segment : 005, Offset : 0107. external length : 000008

EZEIT_OLD : IDOC: Time

internal data type : CHAR

Internal length : 000006 characters

Position in segment : 006, Offset : 0115. external length : 000006

ACTION : Action code for the item

internal data type : CHAR

Internal length : 000003 characters

For more information use the idoc type see the structure in we60.

Thanks,

Pramod