CLOI_CHANGES_UPL_31 doesn't work well

[Former Member]

Dear Experts,

I'd like to dispatch a planned order with specified date&time through BAPI or FM.

I'm testing the FM "CLOI_CHANGES_UPL_31",

but it doesn't work well.

I set the following paramters to dispatch.

Import parameters;

CLOI_IF_PAR-COMMITFLG  = 'C'

           -R3_VERSION = '6.0'

           -MET_FILTER = 'X'

           -MSG_FILTER = 'X'

           -METLOG_REQ = 'X'

           -MSGLOG_REQ = 'X'

           -MSGOBJ_REQ = 'X'

           -ORD_REQ    = 'X'

           -ORDSEQ_REQ = 'X'

           -ORDOPR_REQ = 'X'

           -PLORD_REQ  = 'X'

           -PLORDOPR_R = 'X'

Tables;

CLOI_PLORD_OPRU_IMP-PLNUM = '90000000'

                   -VORNR = '0010'

                   -FIELD = 'METHOD'

                   -VALUE = 'DISPATCH'

Result;

CLOI_MESSAGE_LOG_EXP-MSGTY ='E'

I got some other return parameters with the error message status.

Why?

I don't know which number I should set on the R3 version, too.

I'm thinking that

I need to set the following paramters to specify the date and time while dispatching.

Import parameters;

CLOI_IF_PAR-COMMITFLG  = 'C'

           -R3_VERSION = '6.0'

           -MET_FILTER = 'X'

           -MSG_FILTER = 'X'

           -METLOG_REQ = 'X'

           -MSGLOG_REQ = 'X'

           -MSGOBJ_REQ = 'X'

           -ORD_REQ    = 'X'

           -ORDSEQ_REQ = 'X'

           -ORDOPR_REQ = 'X'

           -PLORD_REQ  = 'X'

           -PLORDOPR_R = 'X'

Tables;

CLOI_PLORD_OPRU_IMP-PLNUM = '90000000'

                   -VORNR = '0010'

                   -FIELD = 'METHOD'

                   -VALUE = 'DISPATCH'

Tables;

CLOI_PLORD_OPRU_IMP-PLNUM = '90000000'

                   -VORNR = '0010'

                   -FIELD = 'SENDD'

                   -VALUE = 15/06/02

CLOI_PLORD_OPRU_IMP-PLNUM = '90000000'

                   -VORNR = '0010'

                   -FIELD = 'SENDU'

                   -VALUE = 17:00:00

I don't know how I find the field name to specify during dispatch.

Of course, I checked some SCN messages like

but I still don't understand how I should use this FM.

Best regards,

Mei

[rupesh_brahmankar3 · Accepted solution]

Hello Mei,

What the exception error message are you getting?

Which order are you trying to dispatch?

Also refer FAQ note 545860 - FAQ: CLOI_CHANGES_UPL_31 and COMMIT control (COMMITFLG)

Best Regards,

R.Brahmankar

[Former Member · Accepted solution]

Thank you for your reply.

Though I get the error status, I don't get any error message.

Here is my result of CLOI_MESSAGE_LOG_EXP.

INDEX: 1

MSGID: C/

MSG: 007

MSGV1: 0010

MSGV2: 0

I'm trying to dispatch a planned order ( The number '90000000' is an example number.)

I checked the note 545860,

but I still don't understand how to use this FM.

Though I execute this FM one time,

I get the error as above,

Best regards,

Mei

[rupesh_brahmankar3 · Accepted solution]

Hello Mei,

If there is no order to be changed, the system should return a success code '10' (error).

r3_version  = '60'.

Please refer help links

CLOI_IF_PAR - Supply Chain Planning Interfaces (LO-SCI) - SAP Library

CLOI_PLORD_OPRU_IMP - Supply Chain Planning Interfaces (LO-SCI) - SAP Library

Best Regards,

R.Brahmankar

[Former Member · Accepted solution]

Thank you for your reply.

I used R3 version "60" instead of "6.0" and executed the  FM in TRCD:SE37.

The result was the same.(The error number was 10 again!)

I checked the links which you sent me,

but I still don't solve the problem...

We don't use any optimization system nor external system.

We only want to create a new ABAP program for dispatching with date and time.

Is the right way to struggle with this FM for me?

I mean is there any other solutions for my request?

Best regards,

Mei

[rupesh_brahmankar3 · Accepted solution]

Hello Mei,

Order number should be 10 digits, in your case it showing only 8 digits.

Also try to dispatch the order in CM25 if you are bale to do that then it should work with FM CLOI_CHANGES_UPL_31.

Best Regards,

R.Brahmankar

[Former Member · Accepted solution]

Thank you for your kindness.

Now, I could dispatch a planned order through this FM .

The reason why I hadn't been able to dispatch it was I didn't set the parameter for "APLFL".

Here is my parameters;

Import parameters;

CLOI_IF_PAR-COMMITFLG  = 'C'

           -R3_VERSION = '60'

           -MET_FILTER = 'X'

           -MSG_FILTER = 'X'

           -METLOG_REQ = 'X'

           -MSGLOG_REQ = 'X'

           -MSGOBJ_REQ = 'X'

           -ORD_REQ    = 'X'

           -ORDSEQ_REQ = 'X'

           -ORDOPR_REQ = 'X'

           -PLORD_REQ  = 'X'

           -PLORDOPR_R = 'X'

Tables;

CLOI_PLORD_OPRU_IMP-PLNUM = '90000000'

                   -PLNFL   = '0'

                   -VORNR = '0010'

                   -FIELD = 'METHOD'

                   -VALUE = 'DISPATCH'

Next, I try to dispatch with specifying finish date and time.

Tables;

CLOI_PLORD_OPRU_IMP-PLNUM = '90000000'

                   -PLNFL   = '0'

                   -VORNR = '0010'

                   -FIELD = 'METHOD'

                   -VALUE = 'DISPATCH'

Tables;

CLOI_PLORD_OPRU_IMP-PLNUM = '90000000'

                   -PLNFL   = '0'

                   -VORNR = '0010'

                   -FIELD = 'SSEDZ'

                   -VALUE = '170000'

Tables;

CLOI_PLORD_OPRU_IMP-PLNUM = '90000000'

                   -PLNFL   = '0'

                   -VORNR = '0010'

                   -FIELD = 'SSEDD'

                   -VALUE = '20150603'

As a result, I get the strange error like this; "Order 000090000000 does not exist".

However, I don't set the "0000" before "90000000" as a planned order number.

It seems that these zero are put automatically.

Or, is it incorrect that value "170000" for latest time when execution of the operation can finish?

When I use TRCD:SE37, I put the number 170000.

Is this the way to input incorrect?

Best regards,

Mei

[rupesh_brahmankar3 · Accepted solution]

Hello Mei,

Order number should be "0090000000" 10 digits.

SSEDZ and SSEDD format seems to be OK

Refer example from OSS note 184471 - Consultation: POI-upload from process orders

AUFNR        EXTAUFNR    APLFL  VORN FIELD      VALUE

43013901    43013901     0      0011 VGW01      0

43013901    43013901     0      0011 VGE01      H

43013901    43013901     0      0011 METHOD     UPDATE

43013901    43013901     0      0010 SSEDD      19991223

43013901    43013901     0      0010 SSEDZ      100000

43013901    43013901     0      0010 METHOD     DISPATCH

Best Regards,

R.Brahmankar

[Former Member · Accepted solution]

Thank you for your reply.

I understand the order number should be 10 digits,

but it seems that the number becomes 12 digits based on the result messge.

Then, I added the external number and changed the sorting order of data like this;

PLNUM     EXTPLNUM   PLNFL  VORN  FIELD      VALUE

90000003   90000003       0           0010     SSEDD   20150603

90000003   90000003       0           0010     SSEDZ    170000

90000003   90000003       0           0010     METHOD DISPATCH

<Before>

PLNUM     EXTPLNUM   PLNFL  VORN  FIELD      VALUE

90000003   0                     0           0010     METHOD DISPATCH

90000003   0                     0           0010     SSEDD   20150603

90000003   0                     0           0010     SSEDZ    170000

As a result, No error occured,

but I didn't get a good result.

It means that dispatch  didn't work without error messages.

So, I cannot check the cause of this because I cannot see any error messages.

Have you ever faced the similar situation which is no error and no execution ?

Best regards,

Mei

[rupesh_brahmankar3 · Accepted solution]

Hello Mei,

I would suggest please try to fist dispatch the planned order through CM25. And check the results and log. If you are able to dispatch it there successfully with desire results then it should work with FM too.

Best Regards,

R.Brahmankar

[Former Member · Accepted solution]

I've just got the good result now!

A planned order was dispatched with specified date and time through this FM

The cause of my last problem was lack of parameter setting...

I'm so sorry for disturbing you.