Prod order creation problem

Hi PP gurus..
Pls help me in problem abt prod order..i creat material with type FERT with order type PP01and go through it all sequence but when i creat prod order abt same system show msg.valuation type INLAND is not allow in in house production..
Regards.and thanx in advance
Amit Naik

Hi
I think while creating material in MM01 you had selected the valuation type which is not define for INhouse production that you are getting this error. See setting for valuation type.
Regards
Abhijit Gautam

Similar Messages

LO-VC Variant Config - update STPO-SANKA field at Plan/Prod Order Creation

Hi All VC Expert,
We are facing an issue with the update by reference characteristic of the field STPO-SANKA Cost relevancy indicator on the BOM.
We are on SAP ECC 6.0 release 700 on Oracle
          Hot Package
               - SAPKA70015 on ERP Cross Application componenent
               - SAPKH60013 on SAP-APPL Logistics and accouting
We are using material variant
We are on the first level of configuration
Classically, we built a procedure to set X to this data base field as below :
$self.STPO_SANKA = 'X'
We assigned this procedure to the relevant items
Here is the result we have:
At the creation of the Plan Order, this is not working
At the creation of the Prod Order, this is not working
When we do a Reload PP master data, this is working very well
On CU50/VA02 when we check the trace, the procedure is executed.
Do somebody have an idea or already facing this and solve it ?
Thanks in advance for your appreciated help.
Edited by: Fabien MAUPIN on Jan 24, 2012 11:49 AM
I still have issue with this object characteristics. I didn't find Oss note to correct the issue.
Do somebody is facing the same issue as me and find a solution ?
Edited by: Fabien MAUPIN on Jan 24, 2012 11:51 AM

Hi Fabien,
I have series of questions to ask.
1. How are you creating the Planned order or Production Order. Is it created directly in PP module or through the requirement transfer from SD.
2. What do you mean by PP master data.
If you trigger the BOM for the planned order or production order from Sales order and some other reqmt trigger, what is your precondition for updating the cost relevancy indicator. If you some script some lines of your process, I can check if you should include the $PARENT clause somewhere. I think the problem lies somewhere in the origin of configuration.

Prod.Order Creation- Using Reference Operation set.

Hi
While creating a production order of particular order type,after entering the quantity and order finish date as today's date(05.06.2007),backward scehduling,it's showing no routing found for the material (as we are using REM-Repetitive manufacturing,we are having rate routing) ,and in the same mesaage box itself I choosed the Reference operation set(that I have created today) and entered the group no,and after entering its showing me an error as <b>Ref. operation set 50000008 is not valid according to the selection conditions</b>,
So I created a routing for the same material nd in MRP4 view of the same material under for selection method i kept blank(Selection by order qunatity) and tried to create Prod.order,and there was no problem,but if the same i'm trying to create using Reference operation set I'm not able to create the Production order.
Kindly give me a solution for this,Is there anything to do with order type dependent parameters of the particular order type?
Thanks & Regards
Raj

Hi,
Is your problem solved ?
One more solution to create a order with reference operation set,is to use a trigger point.
Once you create a reference operation set.
Use T.code co31 to create a trigger point, chosoe create order with reference & choose a system status eg: PCNF. & click the user parameter tab.
The system will aks for the reference operation set no & group counter.
Then assign this reference operation set to the routing operation.
When you do partial confirmation of this operation, this will trigger the generation of a order.
Regards,
Senthilkumar SD

Restrict picking of valuation type at Prod. order Creation

Hi,
We have extend the current semi finish material to Valuation type IH.
While creating production order system automatically assign valuation type IH to the order,
how to restrict this assignment to prod. Order?????????
Regards,
Devendra

Hi,
During order creation system default pick up valuation type under TAB Goods receipt,
Is there any setting into prod. Order dependent parameters,scheduling profile so that system should update valuation type,
I have check into system ,there is no setting for Batch into production order dependent parameters,
pl. suggest.
Regards,
Devendra

Purchase order Creation Problem

Dear All
For Local purchase NB order creation SAP Asking the Account assignement category.
for only particular plant ,It should ask only Service orders. but why its asking the NB orders.
Even Valuation grouping code already assigned for that plant.
Any other settings required..
Please guide..
Regards
Kumnar

Dear All
For Local purchase NB order creation SAP Asking the Account assignement category.
for only particular plant ,It should ask only Service orders. but why its asking the NB orders.
Even Valuation grouping code already assigned for that plant.
"System Throughout the error "Account assignment mandatory for the material 200011"
The material type is verp. and accounting view already extented for this plant
Any other settings required..
Please guide..
Regards
Kumnar

Planned order creation problem

Hello everybody,
When I am creating a planned order manually in MD11, I receive the message "Planned order xxxxx will be created".
Then I receive a popup window telling me "Express document 'Update was terminated' ".
But, when I am having a look in MD04 to see the planned order, I can't see it.
It was still okay yesterday morning, but since yesterday afternoon, no more planned orders can be created manually. Do you have an idea about what can be the reason of this?
It's just like if the order creation was delayed... But for how long, and waiting for what???
Thanks in advance for your help.
Regards,
Rudy

Hi,
There is something issue with ur data while saving..hence it is not saving and throwing the message. so that while upadting data in table is not acccepting.
GOTO SM14->click on ALL UPDATEREQUESTS push button->U will find the reocrds,select ur userid and double click on it,now u can see the module name,select it and double click on it,now u will get one small dialog box,there u can find the abap editor symbol ,click on it..it will take u to the program where it has taken place
Please refer this thread,
Update was terminated
Regards,
R.Brahmankar

Rework Order Creation Problem

Hi,
I have created trigger point in routing. I have also maintained the scheduling parameters for new order type for rework order. When trigger activates during confirmation it goes to the Rework order creation screen but gives the message of
"Scheduling parameters are not defined for production orders"
It is not picking the parameters.
Regards
HHS

Plz also check the assigned rework workcente to the operation.
Apart from order type scheduling parament .You have to consider the master too.Plz check and let us know

Prod order creation using a BOM

Hi Experts,
I am trying to create a production order for a BOM which has one line item. I could create a prod. order for the line item, but when i am trying to create the prod. order for the BOM, I am getting a message "No Default value mentioned for Op. generation for order type PP01 (material name BOM). What do I do?
Pls advise.
Vijay

Hi,
Maintain the default operation for plant & order in OPJG
Manu

Process order creation problem

I am creating a process order . while creating the process order system is throwing error as Auto batch numbering not set up for material type XXXX in plant xxxx . System is not allowing to create process order.
How to resolve the issue.

Check in CORW and switch off batch creation to isolate the problem if needed. Also see whether you have any batch managed compoents for which you have set master data for automatic batch determination.
There is no setting for material types and plant for batch. May be the error message is not correct. What is the message number?

Service order creation problem

Hi Experts, I have a requirement to create a Service order using a BAPI. I'm trying to use the BAPI BAPI_BUSPROCESSND_CREATEMULTI. I found some code related to this BAPI on this forum . THE service order is created
but ibase / component is not filled . How can i give the Ibase through the bapi and in which parameter of the bapi i have to fil this. Could anyone please help me figure out what the problem is . my code is as follows.

Please find the code current thread and below thread.
FUNCTION ZBAPI_SERVICE_SORDER2.
DATA : IS_HEADER            TYPE TABLE OF      BAPIBUS20001_HEADER_INS,
        WA_HDR               TYPE               BAPIBUS20001_HEADER_INS,
        IS_ITEM              TYPE TABLE OF     BAPIBUS20001_ITEM,
        WA_ITEM              TYPE               BAPIBUS20001_ITEM,
       IT_ACTIVITY             TYPE TABLE OF      BAPIBUS20001_ACTIVITY_INS,
       WA_ACTIVITY           TYPE               BAPIBUS20001_ACTIVITY_INS,
        IT_PARTNER             TYPE TABLE OF      BAPIBUS20001_PARTNER_INS,
        WA_PARTNER           TYPE               BAPIBUS20001_PARTNER_INS,
        IT_SALES             TYPE TABLE OF      BAPIBUS20001_SALES,
        WA_SALES             TYPE               BAPIBUS20001_SALES,
        IT_ORG             TYPE TABLE OF      BAPIBUS20001_ORGMAN_INS,
        WA_ORG               TYPE               BAPIBUS20001_ORGMAN_INS,
        IT_PRICING             TYPE TABLE OF      BAPIBUS20001_PRICING,
        WA_PRICING           TYPE               BAPIBUS20001_PRICING,
        IT_SERVICE           TYPE TABLE OF      BAPIBUS20001_SERVICE_OS_INS,
        WA_SERVICE           TYPE               BAPIBUS20001_SERVICE_OS_INS,
        IT_RETURN              TYPE TABLE OF     BAPIRET2,
        WA_RET               TYPE               BAPIRET2,
        IT_PROD             TYPE TABLE OF      BAPIBUS20001_PRODUCT,
        WA_PROD              TYPE               BAPIBUS20001_PRODUCT,"PROCESS_QTY_UNIT -EA
*        IT_SCHED             TYPE TABLE OF     BAPIBUS20001_SCHEDLIN, "QUANTITY
*        WA_SCHED             TYPE              BAPIBUS20001_SCHEDLIN,
        IT_SCHEDLINEs         TYPE TABLE OF     BAPIBUS20001_SCHEDLIN,
        WA_SCHEDLINEs         TYPE              BAPIBUS20001_SCHEDLIN,
        lv_partner_fct1      TYPE               crmt_partner_fct,
        lv_partner_fct2      TYPE               crmt_partner_fct,
        lv_partner_fct3      TYPE               crmt_partner_fct,
        lv_partner_fct4      TYPE               crmt_partner_fct,
        LV_HANDLE            TYPE               CRMT_PRP_HANDLE,
        t_object_to_save     TYPE               crmt_object_guid_tab,
        IT_OBJECT_TO_SAVE    TYPE TABLE OF      crmt_object_guid_tab,
        ts_object            type               CRMT_OBJECT_GUID,
        It1_object_to_save   TYPE TABLE OF      BAPIBUS20001_GUID_DIS,
        W_OBJECT_TO_SAVE     TYPE               BAPIBUS20001_GUID_DIS,
        LV_LOG_HANDLE        TYPE               BALLOGHNDL,
        IT_RETURN1              TYPE TABLE OF     BAPIRET2,
        it_saved_objects     type             crmt_return_objects,
        t_exceptions         type              CRMT_EXCEPTION_T,
        t_objects_not_saved type              CRMT_OBJECT_GUID_TAB,
        WA_INPUT_FIELDS      TYPE              BAPIBUS20001_INPUT_FIELDS,
        IT_INPUT_FIELDS      TYPE TABLE OF     BAPIBUS20001_INPUT_FIELDS,
        ITAB_CREATED_PROCESS TYPE STANDARD TABLE OF BAPIBUS20001_HEADER_INS,
        WA_CREATED_PROCESS   TYPE              BAPIBUS20001_HEADER_INS,
        IT_OBJECTS           TYPE TABLE OF     BAPIBUS20001_OBJECTS,
        WA_OBJECTS           TYPE              BAPIBUS20001_OBJECTS.
DATA:   CV_LOG_HANDLE        TYPE              BALLOGHNDL,
        i_saved_objects      type table of     BAPIBUS20001_OBJECT_ID,
        IT_RET2              TYPE TABLE OF     BAPIRET2,
        WA_SAVed_objects     type BAPIBUS20001_OBJECT_ID,
        g_objnr              type CRMT_OBJECT_ID.
DATA :
        LV_GUID1   TYPE       GUID_32,
        LV_GUID2   TYPE       GUID_32,
        LV_GUID3   TYPE       GUID_32,
        V_OBJNR22 TYPE       IBIN-OBJNR,
        V_GUID16     TYPE       COMT_PRODUCT_GUID,
        V_OBJID    TYPE       COMT_PRODUCT_ID.
*************HEADER-GUID**********
CALL FUNCTION 'GUID_CREATE'
IMPORTING
    EV_GUID_32       = LV_GUID1.
***********ITEM-GUID************
CALL FUNCTION 'GUID_CREATE'
IMPORTING
   EV_GUID_32       = LV_GUID2
*********SCHEDULELINE********
CALL FUNCTION 'GUID_CREATE'
    IMPORTING
      EV_GUID_32       = LV_GUID3
************DATA IN HEADER**********
WA_HDR-GUID = LV_GUID1.
WA_HDR-PROCESS_TYPE = 'YESV'.
WA_HDR-DESCRIPTION = PROCESS_DESCRIPTION.
APPEND WA_HDR TO IS_HEADER.
*************** INPUT FIELDS HEADER**************
CLEAR WA_INPUT_FIELDS.
CLEAR IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID1.
WA_INPUT_FIELDS-REF_KIND = 'A'.
WA_INPUT_FIELDS-OBJECTNAME = 'ORDERADM_H'.
WA_INPUT_FIELDS-FIELDNAME = 'GUID'.
wa_input_fields-fieldname = 'MODE'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID1.
WA_INPUT_FIELDS-REF_KIND = 'A'.
WA_INPUT_FIELDS-OBJECTNAME = 'ORDERADM_H'.
WA_INPUT_FIELDS-FIELDNAME = 'PROCESS_TYPE'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID1.
WA_INPUT_FIELDS-REF_KIND = 'A'.
WA_INPUT_FIELDS-OBJECTNAME = 'ORDERADM_H'.
WA_INPUT_FIELDS-FIELDNAME = 'DESCRIPTION '.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
************DATA IN ITEM**********
WA_ITEM-GUID = LV_GUID2.
WA_ITEM-HEADER = LV_GUID1.
WA_ITEM-ORDERED_PROD = PRODUCT.
WA_ITEM-DESCRIPTION = PROD_DESCRIPTION. "product name
WA_ITEM-ITM_LANGUAGE = 'EN'.
WA_ITEM-ITM_TYPE = ITEM_CAT.
WA_ITEM-NUMBER_INT = ITEM_NO.
WA_ITEM-MODE = 'A'.
INSERT WA_ITEM INTO TABLE IS_ITEM.
*******INPUT FIELDS ITEM*****************
CLEAR WA_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID2.
WA_INPUT_FIELDS-REF_KIND = 'B'.
WA_INPUT_FIELDS-OBJECTNAME = 'ORDERADM_I'.
WA_INPUT_FIELDS-FIELDNAME = 'ORDERED_PROD'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID2.
WA_INPUT_FIELDS-REF_KIND = 'B'.
WA_INPUT_FIELDS-OBJECTNAME = 'ORDERADM_I'.
WA_INPUT_FIELDS-FIELDNAME = 'DESCRIPTION '.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID2.
WA_INPUT_FIELDS-REF_KIND = 'B'.
WA_INPUT_FIELDS-OBJECTNAME = 'ORDERADM_I'.
WA_INPUT_FIELDS-FIELDNAME = 'ITM_LANGUAGE'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID2.
WA_INPUT_FIELDS-REF_KIND = 'B'.
WA_INPUT_FIELDS-OBJECTNAME = 'ORDERADM_I'.
WA_INPUT_FIELDS-FIELDNAME = 'ITM_TYPE'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID2.
WA_INPUT_FIELDS-REF_KIND = 'B'.
WA_INPUT_FIELDS-OBJECTNAME = 'ORDERADM_I'.
WA_INPUT_FIELDS-FIELDNAME = 'NUMBER_INT'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
************DATA IN ACTIVITY**********
WA_ACTIVITY-REF_GUID = LV_GUID1.
WA_ACTIVITY-PRIORITY = PRIORITY.
APPEND WA_ACTIVITY TO IT_ACTIVITY.
*************INPUT FIELDS SALES*************
CLEAR WA_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID1.
WA_INPUT_FIELDS-REF_KIND = 'C'.
WA_INPUT_FIELDS-OBJECTNAME = 'ACTIVITY_H'.
WA_INPUT_FIELDS-FIELDNAME = ' PRIORITY'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
************DATA IN SALES**********
WA_SALES-REF_GUID = LV_GUID1.
WA_SALES-PO_NUMBER_SOLD = SOLD_T0_PARTY.
wa_sales-ref_kind = 'A'.
APPEND WA_SALES TO It_SALES.
*************INPUT FIELDS SALES*************
CLEAR WA_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID1.
WA_INPUT_FIELDS-REF_KIND = 'E'.
WA_INPUT_FIELDS-OBJECTNAME = 'SALES'.
WA_INPUT_FIELDS-FIELDNAME = 'PO_NUMBER_SOLD'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
************DATA IN PARTNER *********
WA_PARTNER-REF_GUID    = LV_GUID1.
WA_PARTNER-REF_KIND    = 'A'.
WA_PARTNER-PARTNER_FCT = '00000001'.
WA_PARTNER-PARTNER_NO = SOLD_T0_PARTY .
wa_partner-ref_partner_handle = '0001'.
wa_partner-display_type = 'BP'.    "Business Partner Number
wa_partner-no_type = 'BP'.        "Business Partner Number
wa_partner-kind_of_entry = 'C'. "entered manually
APPEND WA_PARTNER TO IT_PARTNER.
WA_PARTNER-REF_GUID    = LV_GUID1.
WA_PARTNER-REF_KIND    = 'A'.
WA_PARTNER-PARTNER_FCT = '00000014'.
WA_PARTNER-PARTNER_NO = EMPLOYEE_RESPONSIBLE .
wa_partner-ref_partner_handle = '0001'.
wa_partner-display_type = 'BP'.    "Business Partner Number
wa_partner-no_type = 'BP'.        "Business Partner Number
wa_partner-kind_of_entry = 'C'. "entered manually
APPEND WA_PARTNER TO IT_PARTNER.
WA_PARTNER-REF_GUID    = LV_GUID1.
WA_PARTNER-REF_KIND    = 'A'.
WA_PARTNER-PARTNER_FCT = '00000056'.
WA_PARTNER-PARTNER_NO = SERVICE_EMPLOYEE_GROUP.
wa_partner-ref_partner_handle = '0001'.
wa_partner-display_type = 'BP'.    "Business Partner Number
wa_partner-no_type = 'BP'.        "Business Partner Number
wa_partner-kind_of_entry = 'C'. "entered manually
APPEND WA_PARTNER TO IT_PARTNER.
WA_PARTNER-REF_GUID    = LV_GUID1.
WA_PARTNER-REF_KIND    = 'A'.
WA_PARTNER-PARTNER_FCT = '00000003'.
WA_PARTNER-PARTNER_NO = BILL_TO_PARTY.
wa_partner-ref_partner_handle = '0001'.
wa_partner-display_type = 'BP'.    "Business Partner Number
wa_partner-no_type = 'BP'.        "Business Partner Number
wa_partner-kind_of_entry = 'C'. "entered manually
APPEND WA_PARTNER TO IT_PARTNER.
*INPUT FIELDS PARTENER
CLEAR WA_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID1.
WA_INPUT_FIELDS-REF_KIND = 'A'.
WA_INPUT_FIELDS-OBJECTNAME = 'PARTNER'.
WA_INPUT_FIELDS-FIELDNAME = 'PARTNER_FCT'.
wa_input_fields-logical_key = '0001'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID1.
WA_INPUT_FIELDS-REF_KIND = 'A'.
WA_INPUT_FIELDS-OBJECTNAME = 'PARTNER'.
WA_INPUT_FIELDS-FIELDNAME = 'PARTNER_NO '.
wa_input_fields-logical_key = '0001'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID1.
WA_INPUT_FIELDS-REF_KIND = 'A'.
WA_INPUT_FIELDS-OBJECTNAME = 'PARTNER'.
WA_INPUT_FIELDS-FIELDNAME = 'PARTNER_FCT'.
wa_input_fields-logical_key = '0001'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID1.
WA_INPUT_FIELDS-REF_KIND = 'A'.
WA_INPUT_FIELDS-OBJECTNAME = 'PARTNER'.
WA_INPUT_FIELDS-FIELDNAME = 'PARTNER_NO '.
wa_input_fields-logical_key = '0001'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID1.
WA_INPUT_FIELDS-REF_KIND = 'A'.
WA_INPUT_FIELDS-OBJECTNAME = 'PARTNER'.
WA_INPUT_FIELDS-FIELDNAME = 'PARTNER_FCT'.
wa_input_fields-logical_key = '0001'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID1.
WA_INPUT_FIELDS-REF_KIND = 'A'.
WA_INPUT_FIELDS-OBJECTNAME = 'PARTNER'.
WA_INPUT_FIELDS-FIELDNAME = 'PARTNER_NO '.
wa_input_fields-logical_key = '0001'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID1.
WA_INPUT_FIELDS-REF_KIND = 'A'.
WA_INPUT_FIELDS-OBJECTNAME = 'PARTNER'.
WA_INPUT_FIELDS-FIELDNAME = 'PARTNER_FCT'.
wa_input_fields-logical_key = '0001'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID1.
WA_INPUT_FIELDS-REF_KIND = 'A'.
WA_INPUT_FIELDS-OBJECTNAME = 'PARTNER'.
WA_INPUT_FIELDS-FIELDNAME = 'PARTNER_NO '.
wa_input_fields-logical_key = '0001'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
wa_input_fields-ref_guid = lv_guid1.
wa_input_fields-ref_kind = 'A'.
wa_input_fields-objectname = 'PARTNER'.
wa_input_fields-fieldname = 'KIND_OF_ENTRY '.
wa_input_fields-logical_key = '0001'.
APPEND wa_input_fields TO it_input_fields.
wa_input_fields-ref_guid = lv_guid1.
wa_input_fields-ref_kind = 'A'.
wa_input_fields-objectname = 'PARTNER'.
wa_input_fields-fieldname = 'NO_TYPE '.
wa_input_fields-logical_key = '0001'.
APPEND wa_input_fields TO it_input_fields.
wa_input_fields-ref_guid = lv_guid1.
wa_input_fields-ref_kind = 'A'.
wa_input_fields-objectname = 'PARTNER'.
wa_input_fields-fieldname = 'DISPLAY_TYPE '.
wa_input_fields-logical_key = '0001'.
APPEND wa_input_fields TO it_input_fields.
as follows.
please find below thread.
Edited by: venkatrao veeramaneni on Nov 4, 2011 3:54 PM
Edited by: venkatrao veeramaneni on Nov 4, 2011 3:57 PM

Purchase order creation problem.. me21n

Hi All,
I have the following requirement in creation of PO.
When the Purchase Order of some type, say for eg. in my case its a custom type ZNB denoting intercompany pricing is created from a Purchase Requisition, the system should check the Account Assignment Category of the Items in Purchase Requisition. For the Item that has an account assignment category 9 indicating that the item is for free ( for eg. if a cylinder of chemical gas is considered , them the cylinder/ container should not be billed ), the flag Free should be ticked for this particular item. As a result the Pricing will not be applicable for such an item.
I would like someone to please throw light on how this can be achieved. is there any user exit to get this done ?
Thanks in advance ..
Sharat.

Hi Sharat,
the Badis ME_PROCESS_PO_CUST & ME_PROCESS_PO may be helpful to u...

Error when selecting batch during prod order creation

Hi Gurus,
When selecting batch for production orders components, an error prompted 'Invalid batch, does not match the selection criteria in batch determinat.'
After checking, it is because the classification is not maintained. So I need to re-create in MSC2N.
The question is, how/where should I change back the configurations on checking the batch classification during prod ord?
Thank you.

Kumar,
Please let me know how many Component items are there in the BOM? Out of which how many are Phantom assembly?
It looks like when the BOM is copied to the order it is crossing 9999 items.
I would suggest you to use an intermediate order/material to reduce this number.
I think there was an OSS notes for this to extend the number of character length for BOM items numbering (POSNR).
Hope this helps...Reward your points,
Regards,
Prasobh

Sales order creation problem

dear all my friends
i want to create a sales order from the BAPi BAPI_SALESORDER_CREATEFROMDAT2 but i want to but the material bar code instead of material number in line item of table ORDER_ITEMS_IN - EAN_UPC put i found the flowing error
EAN 4006381157926 does not match material and unit of measure
what should i do

Seems like it's trying to input the scanned material number into the Unit of Measure field and hitting Enter. You need to configure your bar code scanner to hit tab after each scan Material number scan, Quantity Scan.

PO order creation problem

Dear All,
While I am trying to create a PO in dev client system throws an error message "Internal number assignment not defined (plz enter no)" . Message no :06243.
Plz let me know where I ll set this no range .
Regards
Abhijit Das

hi,
first you define no range in OMH6
second one -
go to ---material management -purchasing---purchase order -
define document type ---define insted of that document type which you are define assign the no range --- save
now create po me21n
thanks
santosh.

Capacity availability check during prod order creation

When i create many production order for a particular material with different huge quantities , while doing capacity availability check system issues a message *" No reqmts/caps exists or not relevant to finite scheduling*
Here as per the message i have checked all the possible errors and everything is fine.
As per actual requirements, work centers are overloaded. But here system displays that all work centers are available.
Any help regarding this.

Dear Nandi,
Please refer the below link,
No reqmt/capacity exist or not relevnt for finite scheduling: Mesage: CY298
Regards,
Sundhu

Prod order creation problem

Similar Messages

Maybe you are looking for