Settlement rule auto created in Production Order with Receiver Type as OIT

Hi,
I am creating a production order with material number in CO01. The system is automatically putting OIT in receiver category, in settlement rule.
And its populating the child materials there. I expect the parent material to be populated in the settlement receiver.
In the settlement profile maintained in order type, I have maitained MAT.
Please let me know, why system is autopopulating the role like above.
Regards
SR

Hi,
If you are going to settle the production order to Material, there is no need to enter Allocation structure in Settlement profile unless its used for variance settlement...
Allocation structure has an option to settle to OIT with a settlement cost element or primary cost element...which is why i wanted you to check for that.
Anyways, Follow the thread, this should help you
Change the Settlement Rule
Thx
PG

Similar Messages

Create a production order with variant configurator data

Hello,
Can anyone tell me the way to create a production order with variant configurator data. Is there a BAPI ? an IDOC ?
Is there several steps ?
I have to create an interface which creates automatically PP orders. The data input is a file.
Thanks for your help

Hi,
There are fews BAPI's available for creation of Production Order. They are:
BAPI_PRODORD_CREATE
This bapi will suit to your requirement, as input will be provided from file.
Others are
BAPI_PRODORD_CREATE_FROM_PLORD " this converts planned order to production order
BAPI_PRODORD_CREATE_FROM_REF " this creats production order considering other production order as reference.
Hope your query is answered.
Regards,
Brajvir

Require settlement rule when creating a Prod order

Hello,
Hello,
one of our processes is to fabricate complex tools that will be capitalized and depreciated when completed.
while the tools is being fabricated, we would like to settle regularly the production order to a capital order (AUC) and track the budget for the fabrication.
in this production process we want to require the user to enter a capital internal order in the settlement rule of the production order master data.. this way when Prod order is settled we dont have issues. can you make settlement rule entry as required during production order creation?
any input is appreaciated on the issue. Thanks
Andy

Hi,
There is no standart control for this, but I know a PP user exit which excatly meet you requirement.
PPCO0007---User Exit for Checking or Changing Header Fields During Order
You can first control if it is a production order ( ı think it is a special type to produce auc) that you want to control. Then you can select settlement rule and control and give error message settlement rule is mandotory you can not save. The exit sends a signal that it is not possible to save. For error message you can write code into the exit for the message.

Need a function module to create production order with reference

Hi
I need a function module to create a production order with reference to an existing order. There is no BAPI available for SAP 4.7 release. I found that the function module CO_ZF_PRODUCTIONORDER_CREATE does not create with reference to an existing order.
Any help will be rewarded.
Pavan

Dear Pavan,
Unfortunately there is no FM for this..
Cheers
Nitesh

BAPI to create a production order CO07

Hi guys,
Need a help....i need to create a production order with the following data...
1.final date...2.routing group 3.components screen with all the materials needed
there will be multiple components added..as co-products and as a main material
BAPI_PRODORD_CREATE...can we use this to add multiple materials...and will it fulfill the tcode CO07...
any queries or any sort of info..plz share..
Regards,
Ashok

Thanks for the reply.
In these BAPIs..or FMs...we can add one material or a component...
I want to add a main material...as a first one..
then a component of it....so it goes on..
say i have a main material and 10 components needed and created in a single production order...
any info???

Variance calculation for production order with settlement receiver as SDI

Hi...
I have one query reference to Variance calculation for production order with settlement receiver as SDI(Sales document item).
I am working on Varaint configuration with strategy 25(Make-to-order for configurable material) with requirement class 046.
I have created sales order ref. to configurable material,subsequently created planned order & then converted to production order.
In production order settlement receiver is SDI(Sales document item).
While doing production confirmation ,variance has been created.
Now during variance calculation KKS2, I have got error message as no suitable settlement rule found for object Order no.
Is there any way to come out of this?Or variance calculation KKS2 is not applicable with settlement receiver as SDI(Sales document item).
Pl. guide
Redards
Tushar

Hi
In case of non valuated material, concept of variance does not apply...
Variance is Actual Cost - Cost of Goods receipt posted in stock.. If the later value is zero, your entire actual cost is variance... That is one way of saying it
But, in SAP, var not calculated in case of non valuated material and that makes sense as well.. Since you are in MTO scenario, it would make sense to analyse costs vs revenues @ sale order level as each SO will be unique in itself
Regards
Ajay M

Error message while creating production order with KMAT material strategy25

Hi PP Gurus I am running variant configuration cycle...Strategy 25, Custermer Req KEK (KMAT Matrl)
Sales order & MRP Picked the components correctly as per the dependencies
written. So Planned order generated against sale order.
When I tried to convert planned order to Production order...I am getting the
below error message..
Error Message:
You cannot make an assignment to make-to-order stock Message no. CO684
Diagnosis The component cannot be allocated to an individual stock because
make-to-order production and engineer-to-order production cannot be executed
with this order.
A possible cause is that you are trying to create an order with reference to a
sales-order/project, where an account assignment to a sales order/project is not
allowed in the settlement profile that is assigned to the chosen order type.
This is inconsistant.
System response The following responses are possible:
Order processing is cancelled.
The system resets the special stock indicator back to the original value.
Procedure Choose another order type.
I used order type with SD1 as settelement profile.
OVZG: default 046, settlement profile = SD1
OPJH: Settlement profile = SD1
Plz through some light on this if u have worked on Variant Configuration/MTO
settlements.
Question:
1) Is creation of production order with KMAT material supported by SAP?
2) If yes, why the above error occurs?
Waiting for Ur reply
With Best Regards

Dear R.Brahmankar,
I have check on the note, but it is not relevant to ecc6. The current system default setting is :
Standrad setting for reqt class 046
Special Stock E
Acct Assgt Cat. M
Valuation M
Settlmt Profile SD1
However if I change the Acct Assgt Cat. from M to E. It resolve the problem. I would like to know is this the right solution?
Config in Acct Assgt M
Consumption Posting = E
Config in Acct Assgt E
Consumption Posting = ' '
In F1 key of Consumption Posting field it shown following:
To flag the sales order item as cost- and revenue-carrying, enter an "E" (settlement via sales order).
If you do not wish to flag the sales order item as cost- and revenue-carrying, do not enter anything.
Dependencies
If you are working with nonvaluated sales order stock, always flag the sales order item as cost- and revenue-carrying.
If you are working with valuated sales order stock:
In the case of complex make-to-order production, flag the sales order item as cost- and revenue-carrying
In the case of sales-order-related mass production, do not flag the sales order item as cost- and revenue-carrying
Should we change to E?
Regards,
Ong

Automatic creation of settlement rule while creating sales order

Hi Friends,
Can any one help me how to create settlement rule automatically while creating sales order i.e saving sales order. Is there any function module or any badi which can be used.. please suggest.
thanks
bobby

Hi,
Here is the solution , First Create a sustitution by going into OPSN Transaction , only user exit say 'U902'
and write the form routine in Program named 'ZRGGBS000'
The code is below ,
*&      Form U902
   Automatic Generation of Settlement Rule For WBS and Company 4180
FORM u902.
Exit For Automatic Settlement Rule Creation for WBS Billing elements
IF sy-tcode = 'CJ20N' or sy-tcode = 'CJ01' or sy-tcode = 'CJ02'.
    DATA   lv_proj TYPE ps_pspid.
    lv_proj = proj-pspid.
    EXPORT lv_proj TO MEMORY ID 'PSPID'.
Calling YGPS_CJB1EXEC Program For Creating Settlement Rule
    SUBMIT ygps_cjb1exec AND RETURN.
ENDIF.
ENDFORM.                                                    "u902
*& Program YGPS_CJB1EXEC
PROGRAM ygps_cjb1exec.
   Automatic Generation of Settlement Rule For WBS and Company 4180
Called From Exit For Automatic Settlement Rule Creation for WBS Billing elements
DATA: bdcdata_wa TYPE bdcdata,
      bdcdata_tab TYPE TABLE OF bdcdata,
      itab TYPE TABLE OF bdcmsgcoll.
DATA :lv_currm LIKE bkpf-monat,
      lv_curry LIKE bkpf-gjahr,
      lv_prevm LIKE bkpf-monat,
      lv_prevy LIKE bkpf-gjahr,
      lv_proj TYPE ps_pspid,
      lv_mode TYPE c,
      lv_time TYPE sy-uzeit.
DATA :g_datfm            LIKE usr01-datfm,
      g_dd(2)            TYPE c,                         " Day
      g_mm(2)            TYPE c,                         " Month
      g_yyyy(4)          TYPE c,                         " Year
      g_sydatum(10)      TYPE c.
IMPORT lv_proj FROM MEMORY ID 'PSPID'.
lv_mode = 'N'.
CLEAR bdcdata_wa.
bdcdata_wa-program = 'SAPLKAZB'.
bdcdata_wa-dynpro   = '1000'.
bdcdata_wa-dynbegin = 'X'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'BDC_CURSOR'.
bdcdata_wa-fval = 'PRZB-VARIANT'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'PRZB-VARIANT'.
bdcdata_wa-fval = 'ZGPS0001'.
APPEND bdcdata_wa TO bdcdata_tab.
CALL FUNCTION 'GET_CURRENT_YEAR'
EXPORTING
    bukrs = '4180'
IMPORTING
    currm = lv_currm
    curry = lv_curry
    prevm = lv_prevm
    prevy = lv_prevy.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'RKAUF-FROM'.
bdcdata_wa-fval = lv_currm.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'RKAUF-GJAHR'.
bdcdata_wa-fval = lv_curry.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'BDC_OKCODE'.
bdcdata_wa-fval = '=VARC'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-program = 'RKPSEL00'.
bdcdata_wa-dynpro   = '1000'.
bdcdata_wa-dynbegin = 'X'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'BDC_CURSOR'.
bdcdata_wa-fval = 'CN_PROJN-LOW'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'CN_PROJN-LOW'.
bdcdata_wa-fval = lv_proj.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'CN_PSPNR-LOW'.
bdcdata_wa-fval = space.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'CN_NETNR-LOW'.
bdcdata_wa-fval = space.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'CN_ACTVT-LOW'.
bdcdata_wa-fval = space.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'CN_MATNR-LOW'.
bdcdata_wa-fval = space.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'BDC_OKCODE'.
bdcdata_wa-fval = '/00'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'BDC_OKCODE'.
bdcdata_wa-fval = '=SAVE'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'BDC_OKCODE'.
bdcdata_wa-fval = '=VBAC'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-program = 'SAPLSPO1'.
bdcdata_wa-dynpro   = '0100'.
bdcdata_wa-dynbegin = 'X'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'BDC_OKCODE'.
bdcdata_wa-fval = '=YES'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-program = 'SAPLKAZB'.
bdcdata_wa-dynpro   = '1000'.
bdcdata_wa-dynbegin = 'X'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'RKAUF-BATCH'.
bdcdata_wa-fval = 'X'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'RKAUF-TEST'.
bdcdata_wa-fval = space.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'BDC_OKCODE'.
bdcdata_wa-fval = '=RUN'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-program = 'SAPLKABA'.
bdcdata_wa-dynpro   = '0210'.
bdcdata_wa-dynbegin = 'X'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'KABA01-JNAME'.
bdcdata_wa-fval = 'CJB1_EXEC'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'BDC_SUBSCR'.
bdcdata_wa-fval = 'SAPLKABA'.
APPEND bdcdata_wa TO bdcdata_tab.
Extract the date format from the user settings
PERFORM f_get_dateformat CHANGING g_datfm.
Changing the current date format to User Profile Date Settings
PERFORM f_format_date USING   g_datfm
                              sy-datum+4(2)
                              sy-datum+6(2)
                              sy-datum+0(4)
                     CHANGING g_sydatum.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'KABA01-STDAY'.
bdcdata_wa-fval = g_sydatum.
APPEND bdcdata_wa TO bdcdata_tab.
lv_time = sy-uzeit + 30.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'KABA01-STTME'.
bdcdata_wa-fval = lv_time.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'KABA01-PRIKZ'.
bdcdata_wa-fval = space.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'BDC_OKCODE'.
bdcdata_wa-fval = '=TAKE'.
APPEND bdcdata_wa TO bdcdata_tab.
Calling Transaction 'CJB1' for creating settlement rule
CALL TRANSACTION 'CJB1' USING bdcdata_tab MODE lv_mode .
IF sy-subrc = 0.
ENDIF.
*&      Form F_GET_DATEFORMAT
      This subroutine returns the date format in the user setttigs
     <--P_G_DATFM Date Format
FORM f_get_dateformat CHANGING p_g_datfm.                   "#EC *
SELECT SINGLE datfm FROM usr01 INTO p_g_datfm
WHERE bname = sy-uname.
ENDFORM.                    " F_GET_DATEFORMAT
*&      Form F_FORMAT_DATE
      This subroutine returns the date as per the user settings
     -->P_G_DATFM Date Format
     -->P_G_MM Month
     -->P_G_DD Day
     -->P_G_YYYY Year
     <--P_G_DATE Date
FORM f_format_date USING    p_g_datfm
                            p_g_mm
                            p_g_dd
                            p_g_yyyy
                   CHANGING p_g_date.                       "#EC *
CONSTANTS: c_dot VALUE '.',
             c_slash VALUE '/',
             c_dash VALUE '-',
             c_1 VALUE '1',
             c_2 VALUE '2',
             c_3 VALUE '3',
             c_4 VALUE '4',
             c_5 VALUE '5',
             c_6 VALUE '6'.
DATA: l_day(2),
        l_month(2).
l_day = p_g_dd.
l_month = p_g_mm.
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
    EXPORTING
      input = l_month
    IMPORTING
      output = l_month.
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
    EXPORTING
      input = l_day
    IMPORTING
      output = l_day.
CASE p_g_datfm.
    WHEN c_1.
      CONCATENATE l_day l_month p_g_yyyy INTO p_g_date
          SEPARATED BY c_dot.
    WHEN c_2.
      CONCATENATE l_month l_day p_g_yyyy INTO p_g_date
       SEPARATED BY c_slash.
    WHEN c_3.
      CONCATENATE l_month l_day p_g_yyyy INTO p_g_date
          SEPARATED BY c_dash.
    WHEN c_4.
      CONCATENATE p_g_yyyy l_month l_day INTO p_g_date
          SEPARATED BY c_dot.
    WHEN c_5.
      CONCATENATE p_g_yyyy l_month l_day INTO p_g_date
          SEPARATED BY c_slash.
    WHEN c_6.
      CONCATENATE p_g_yyyy l_month l_day INTO p_g_date
          SEPARATED BY c_dash.
ENDCASE.
ENDFORM.                    " F_FORMAT_DATE
thanks
bobby

Create production order with "bespoke" component list

Hi
I am investigating how I can create a production order which has to use a 'bespoke' component list, i.e., I don't want to use the BOM application. The scenario is that an external solution comes up with the 'best' component list and SAP doesn't have that information.
Obviously I can use the dreaded BDC / call transaction on CO01, but could I use something nicer?
I have ticked off my list so far:
a) the userexits and Badis won't allow direct manipulation of RESB, it's only import parameter...
b) I looked up the POI (function module CLOI_CHANGE_UPL_31), but it diesn't allow updates to the component list.
c) Also the BAPI_PRODORD_CREATE/CHANGE doesn't allow updates to the components.
d) Is there a convenient enhancement spot anyone knows of which could be used (e.g. in FuGr COMK?)
My best option might be this one, does anyone have experience?
e) The function module BAPI_ALM_ORDER_MAINTAIN was developed for CS/PM orders. Does it work for PP orders?
Appreciate any help on this!
BJ

I'm also trying to add a component in a PP order but the Bapi return the message "Method SAVE is not provided for object COMPONENT"; I'm investigating

BAPI-To create production orders with reference to sales order & item

Hi,
Can anyone tell me which is the best method to create open production orders?
Is there any BAPI available for creating production orders with reference to sales order & item.
I tried this BAPI "BAPI_PRODORD_CREATE".
I am getting pop up to enter serial number while executing the custom program.
Which table contains the serial number(effectivity parameters)?.

I have custom screen fields on notification service!
i think a bdc is better.

Co- Product Error while creating a production order

Hi,
While performing the Co-Products Approtionment at the time of creation of Production order..
we are facing a problem regarding cost apportionment I have crated a Source Structure and the cost element is assigned to that Source Structure but still iam facing this issue
kindly help me out.
the error msg is
Debit with cost element 9460404 cannot be settled.
Message no. KD549
Diagnosis
Costs/revenues exist for cost/revenue element 9460404. This cost/revenue element was given source assignment 40 in the source structure (-> settlement rule for sender -> parameters). However, there is no distribution rule with settlement type FUL for this source assignment or the total of the percentages for the rules is less than 100.
Note:
Full settlement settles all the costs and revenues which have occurred up to the settlement period and have not already been settled. In the case of periodic settlement, you can configure the settlement profile so that all the costs occurring in the settlement period are settled, or if an amount less than 100% can be settled.
Procedure
Maintain the distribution rules for source assignment 40 and settlement type FUL or use periodic settlement to settle less than 100%. Change the settlement profile for the sender as necessary.
Change settlement profile
Note:
Cost and revenue elements receive source assignment " " if you have not entered a source structure in the settlement rule parameters.

Hi Krishna Murthy I went through the note but i couldnt recive a big help from that note.
I will explain the step by step process that i have done.
I am attaching the Screen shots of the issue.
1. For co-products I have created a source structure and Sec. Cost Elements were assigned in the source structure.
2. The source structure was assigned in the Material Master for co-products equally distrubuting the amount between 2 materials.
3. When we are trying to create a production order the error was displayed but the costs was getting calculated properly.
4. When I was settling the production order the same error was getting displayed.
I have tried various methods to resolve it.
1. I have created a periodic settlement rule and tried to settle but it didnt work
2. I have assigned the source structure in the settlement profile this also didnt work.

Settlement rule does not exists in order number.

Hi All,
I have been recieving a error while trying to save the Production order. The error reads as "Settlement rule does not exixts in order". But fact is that order has settlement rule. Also there is a default setting done in order type settlement profile because of which settlement rule is created automatically.
Now there is a way around. We calculate cost manually and then we go to settlement rule and check for error. Once we do so the order is good to save.
But we are not able to save it automaticaaly after release. This issue occurs when we try to release the order and then after releasing the order we try to save it.
Please help us on this issue.

Hi Prabhakar,
Thanks for your input. But the said setting was already done while implementation. All the material except this material has the issue. We are able to realease the order properly for the material except this one. And since go live we are using this material for first time.
We did a work around. We copied this material and recreated a new material with reviced part number. That one is working fine in lower client. We have now no idea how could one material all the same data like material master and routing and BOM and work centers can work properly whicle failing for other.
We are trying to debug this will let you all know if we find the solution. Till then if you all have any idea any prior experience, please let me know.

Create a Production order for rework

Hi,
I would like to create a Production order for rework.
But I don't want to do it in the master PO with trigger point.
I would like to create a new PO for rework and asign to account to the old or master PO.
I've tried to do it but I want to know if it's correct.
CO07, maintained the qty, in the settlement rule maintained (category= order,settlement reciever= master PO number) released the order and by confirmation where can I maintain the qty? (as Yield or as rework qty)
Thanks

Hi,
Use T code CO07- creation of PO w/o material, settelment rule as u mentioned and the quantity has to be maintained in rework.
When u confirmed the order and settel it, it will be settel againts the main order.
Regards
JDB

Settlement rule copied from reference internal order

Hi
How to manage that no settlemnt rule will be copied from reference order into the new internal order I´m creating in transaction KO01? Is it a configuration issue?
Please advise.
Anna

HI,
the reason for creating an internal order "with reference" is to transfer all infos to the new order (even the settlement rule). So after "creation with reference" the settlement rule is copied. If its not the one you need:
1: take a reference order that fits your requirement.
2: for order creation without reference use a "model" order, this "model" order can be assigned to the order type in T-code KOT2_OPA and works similar as a reference, but if the model order does not contain a settlement rule, the created order also does not).
3: change/delete the created settlement rule from the new order.
Best regards, Christian

Report for Production orders with name of Customers

Dear Expert,
Kindly suggest to view the production orders with customer numbers for which the sales orders is created.
I tried in MB51 with layout settings but the customer number comes out be blank despite the sales order number is populated for an production order.
Kindly suggst a way or any report in the system to get the corresponding information of production order number and corresponding customer name mentioned in the sales order .
Thanks in advance for your help and inputs..
Best regards,
Nitish jain

Nitish,
MB51 is a Material Document list. Many production orders exist that have no entries in this report, so it would be an unlikely candidate to be a solution for your requirement..
The standard production order reporting tool is COOIS. The output for MTO orders can be configured to display Sales order and Item and Soldto.
Obviously, displaying even the customer order number in COOIS is impossible in a MTS scenario.
In addition, a user experienced in using SAP Query (SQVI or SQ01/SQ02/SQ03) could also create a production order report without having to know ABAP, by properly linking tables AFKO, AUFK, AFPO (production order data) with VBAK (sales order header data) to get customer number, and KNA1 to get customer name..
If you are not expert in SAP Query, I suggest you discuss this requirement with a local ABAPer.
If you are feeling like educating yourself in the wonders of SAP query, try this doc. Although old, SAP query hasn't changed very much since this document was written.
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVQUE/BCSRVQUE.pdf
Rgds,
DB49
Edited by: Dogboy49 on Apr 20, 2010 10:47 PM

Settlement rule auto created in Production Order with Receiver Type as OIT

Similar Messages

Maybe you are looking for