topic Re: BAPI_ROUTING_CREATE / Material Component Allocation in Application Development and Automation Discussions

BAPI_ROUTING_CREATE / Material Component Allocation

90070279 — Tue, 26 Oct 2004 16:14:06 GMT

I'm using BAPI_ROUTING_CREATE in my own BAPI to create routings. The routing is being created when I turn off the component allocation table and all is fine. When I turn on that part, I get an error that states: A CMCL 105 Sequence or Operation are not contained in worklist or are invalid.

In the BAPI1012_COM_C structure I'm sending:

Activity(operation) of '9000',

Backflush = 'X',

Sequence_NO = '0',

Valid From Date and

OPERATION_ID of 'VORG9000' per the documentation.

I tried a sequence number of '1' and that didn't help so I'm led to believe it's something wrong with my OPERATION_ID.

Anyone have some ideas as what could be wrong given the information provided?

Thanks,

Tim Stadler

Menasha Corporation

Re: BAPI_ROUTING_CREATE / Material Component Allocation

Former Member — Tue, 26 Jul 2005 04:28:17 GMT

Hi Am facing the Same Problem now. Did you get any solution for this.

PLease let me know.

THanks

Shekar

Re: BAPI_ROUTING_CREATE / Material Component Allocation

Former Member — Tue, 26 Jul 2005 06:30:03 GMT

Component allocation is done under the operation level so the hierarchy is something like this...

Routing Number.

-- Alternative Number

Sequence

Operation

component allocation.

Therefore in order to allocate components u have to use valid operations and sequence so that the component can be allocated under that sequence and operation.

Please make sure that the operation and sequence numbers that u have entered in the component allocation structure is present in the operation and sequence structures.

But then by default sequence number 0 is generated i guess it is something to do with the operation number.

Re: BAPI_ROUTING_CREATE / Material Component Allocation

90070279 — Thu, 18 Jan 2007 19:30:32 GMT

Here is what I'm sending now and it works fine. I think it should be obvious which are my internal work fields and tables.

w_bapi1012_com_c-activity = '9000'.

w_bapi1012_com_c-backflush = ' '.

w_bapi1012_com_c-sequence_no = '000000'.

w_bapi1012_com_c-valid_from = p_datuv. " sy-datum.

w_bapi1012_com_c-valid_to_date = '99991231'.

w_bapi1012_com_c-operation_id = ' '. "'VORG9000'.

w_bapi1012_com_c-bom_no = w_mast-stlnr.

w_bapi1012_com_c-alternative_bom = '01'.

w_bapi1012_com_c-plant = t_output-zqdwerks.

w_bapi1012_com_c-material = w-matnr.

w_bapi1012_com_c-bom_type = 'M'.

w_bapi1012_com_c-item_no = t_zero2-zrobmline.

w_bapi1012_com_c-item_id = '00000001'.

w_bapi1012_com_c-bom_type_root = 'M'.

w_bapi1012_com_c-bom_no_root = w_mast-stlnr.

w_bapi1012_com_c-alternative_bom_root = '01'.

append w_bapi1012_com_c to t_bapi1012_com_c.

Thanks,

Tim