The SAP Fan Club Forums

Hi Stevie I assume your confirmed operation time do not directly correlate to the confirmed quantity (i.e. 1PC = 10min, 2PC = 20min...), right? If so, then I had a similar requirement once and I did not find any other solution than to programm my own "CO12" by using BAPI_PRODORDCONF_CREATE_TT and ch...

Hi there

Sounds like the message is coming out of RCR05GEN. Check if you are already using your formula ZAP003 in a standard value key. If yes, remove it there or create a new formula and try again.

JohnnyB

Hi there

We use batch input sessions (SHDB) for copying BOMs and routings.

CEWB is also able to copy BOMs and routings. However, not able to mass copy, since background processing not possible.

JohnnyB

Hi KB_MANI

Are there any other requirements for these components? Please check in CO09.

JohnnyB

Hi Kevin

You can have a look at SAP note 1467234. It contains a correction for this problem, which is caused by a kernel patch.

JohnnyB

Hi CJ, If you are using capacity leveling, you could have a look at the strategy profile in SPRO (tcode OPD0). There is a flag called "Operation must lie entirely within a period split". And F1 help says: "Specifies that when dispatching on the period split the start and finish date of the operation...

Hi Jim You could maybe have a look at this: [url]http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PPBDEWB/PPBDEWB.pdf[/url] If you have specific problems with CEWB, you might find some SAP notes at SAP Support Portal. Esp. your excel problem sounds a bit SAPgui-related. JohnnyB P.S: CEWB can ...

Hi there

If you double-click on below mentioned message in the status line, you'll get a help popup which navigates you to the transactions that need to be executed:

Postprocess incorrect goods movements (COGI)
Postprocess flagged goods movements (CO1P)

JohnnyB

Hi wken The workcenter that you see on top is the planned workcenter as it is maintained in the operation. This also appears on 'personnel/additional data' view as "Planned for confirmation" and as the default value for confirmation. It can be overwritten, if the operation actually took place on a d...

Hi KB_MANI, I can only talk about origin = 2. Such CO16n entries are very often caused by confirmations done by BAPIs (e.g. BAPI_PRODORDCONF_CREATE_HDR or BAPI_PRODORDCONF_CREATE_TT) with parameter POST_WRONG_ENTRIES <> 0: 0: Neither confirmations with errors nor confirmations that cannot be process...

Hmm, interesting. You get me really suprised her! :shock: Please let me know if there really is a way. I remember that since 4.6A it is possible to "overwrite" the standard value text with a different activity text. However, CO12 is a mass transaction. Therefore you could (theoretically) confirm ope...

Hi Kholargol CO11n confirmation profiles are not vaild for CO12. And I don't think it is possible to change the activity texts. If I remember correctly, they are defined in DDIC and cannot be changed. I also tried SHD0 with CO12 some time ago and gave up on it, because at the very end (somewhere in ...

Hi there

Do you have IS-ADEC active? Please have a look at SAP note 1288042 ("Routing can not be saved in trx CA01"). Seems like a bug.

JohnnyB

Hi there

Do you use online printing or background printing? In the latter case you just get a message "...marked for background...".

You can also check if the control keys in your operation allow printing.

JohnnyB

Salut picsou Under certain circumstances (see SAP note 442966) AFFW entries are being created, even though they are not error records, but request records. That's why you cannot see it in COGI. Check transaction CO1P instead. It's also recommended to schedule program CORUPROC as a background job. Jo...