Hi Everyone!

We are in the process of migrating from b2 to c4. in our newly setup c4 company, we cannot access the price field (tdsls041.pric) of the maintain so lines session.

We are using the standard session; the field type is also set to "input"; all our items are cost price calculated.

After the order qty field is filled-up, the cursor jumps to the amount field?! skipping the price field!!

Any parametric set-up we missed?

Thanks for your time!

There is a different behaviour of the session when the SO-line is inserted and when you change it (second access). Aren't you able to change the field in any case?

Regards,

Martin

In standard situations, unless the order quantity is 0 or you have made certain specific selections off of the inventory shortage pop-up menu, you should go to the price field. Have you altered the field sequence at all?

Originally posted by Martin Jung
There is a different behaviour of the session when the SO-line is inserted and when you change it (second access). Aren't you able to change the field in any case?

Regards,

Martin

thanks martin! yes i wasn't able to access the field in any case. I'm so sorry that i'm such in a hurry i forgot to include more details.

actually there is this error message that appears after i keyed in the order qty, "Actual calendar not found when planning forward for work center on this date with 0 time units of planning time".

i was able to work around this error by updating our company calendar in the process module.

so sorry for the lack of info...

thanks for your time.

Originally posted by evesely
In standard situations, unless the order quantity is 0 or you have made certain specific selections off of the inventory shortage pop-up menu, you should go to the price field. Have you altered the field sequence at all?

hi evesely! I'm so sorry that i'm such in a hurry i forgot to include more details.

actually there is this error message that appears after i keyed in the order qty, "Actual calendar not found when planning forward for work center on this date with 0 time units of planning time". which i just ignored, thinking it has not effect at all...

i was able to work around this error by updating our company calendar in the process module.

so sorry for the lack of info...

thanks for your time.