Validate cost center in settlement rule while creating WO in IW31

Hi All,
I have a requirement to check whether the cost centers in settlement tab is blocked or not. If it is blocked need to give an error.
Is it possible to implement this using an user exit?..
Thanks,
Spandana

Hi Chetan,
I agree with you that when PR is created thro repair order the A/C assignment category will be 'F',I am not concerned about that and its a SAP std.I am concerned about the automatic cost center population on the PR created from that order.I'll explain you in detail - It goes like this, We are creating a Service Order in IW31for a material X and this material goes sequentialy in operation which it requires, it depends on the control key SM01 whether the operation is to be processed internally or externally,So when it goes for external processing for which the key SM02 is configured and while saving this order a PR is created from this order and as you said this this PR will have A/c assignment category 'F' and its relevant G/L a/c and the order in it.So if you check the cost center field which is in between this G/L a/c and the order it will not appear as it has to be entered manually.So i need this to be automatically determined.
Hope this clarifies.
Thx
Benny

Similar Messages

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

Settlement rule while creating service order

Hi Gurus,
1. can someone help me in knowing what should be passed as receivers key while updating settlement rule if i am using Sales Order for settlement ; sales order, sales order item, object number of item or something else because i tried to pass all of these but not working.
2. I pass receiver category as SDI.
Kindly help asap.
Thanks,
Ritu

Hi Gurus,
1. can someone help me in knowing what should be passed as receivers key while updating settlement rule if i am using Sales Order for settlement ; sales order, sales order item, object number of item or something else because i tried to pass all of these but not working.
2. I pass receiver category as SDI.
Kindly help asap.
Thanks,
Ritu

Purchase Requisition - Validate Cost Center

Hi,
I need to check the data when creating a Purchase Requisition with reference to an existing Purchase Requisition. Currently, I am using the user exit EXIT_SAPLMEREQ_005 to carry out these checks.
One of the checks that I need to do is to validate Cost Center. However, in this user exit, there is no cost center found in any of the imported parameters. Hence, I tried to use the function module 'COBL_RECEIVE'. However, the Cost Center retrieved is not refreshed and is incorrect. Are there any other ways where I can retrieve the correct Cost Center that is populated from the reference Purchase Requisition?
Will appreciate any help in resolving this issue.
Thanks lots.
Cheers,
Liyan

Hi
use the BADI in SE18 Tcode
ME_REQ_POSTED
implement this and use
the Method POSTED has the parameter IM_EBKN which has KOSTL field
this will work
see the sample code for this BADI
BAdI Name: ZPUR_RFQ (Implementation name) Purchase Requisitions
Definition Name: ME_REQ_POSTED
Interface Name : IF_EX_ME_REQ_POSTED
Implementing Class: ZCL_IM_PUR_REQ
Method :            POSTED
METHOD if_ex_me_req_posted~posted .
TYPE-POOLS: pgrt.
DATA: t_txpdat TYPE STANDARD TABLE OF txpdat.
DATA: s_txpdat TYPE txpdat.
DATA: t_ident TYPE pgrt_t_obj_ident.
DATA: s_ident TYPE pgrt_obj_ident.
DATA: ident_tmp TYPE eketkey.
DATA: nmrid_init TYPE txpdat-nmrid.
DATA t_obj_event TYPE pgrt_t_obj_event.
DATA s_obj_event TYPE pgrt_obj_event.
DATA t_event     TYPE pgrt_t_event.
DATA s_event     TYPE pgrt_event.
DATA change_yes TYPE c.
    IF l_s_eban-estkz NE 'B'.
      CLEAR v_mtart.
      SELECT SINGLE mtart INTO v_mtart FROM mara WHERE matnr = l_s_eban-matnr.
      IF v_mtart EQ 'ZERS' OR v_mtart EQ 'FHMI' OR v_mtart EQ 'UNBW'.
        MESSAGE e000(zm_msg) WITH 'You are not allowed' 'to create PR for stock items'.
      ENDIF.
    ENDIF.
    IF l_s_eban-knttp NE 'F' OR l_s_eban-pstyp NE '9'.
      IF l_s_eban-knttp NE 'A'.
        IF ( l_s_eban-pstyp NE '9' AND l_s_eban-pstyp NE 'D' ) AND l_s_eban-matnr EQ space.
          MESSAGE e000(zm_msg) WITH 'You cannot create' 'a PR without material number'.
        ENDIF.
      ENDIF.
    ENDIF.
ENDLOOP.
ENDMETHOD.
reward points if useful
regards
Anji

Cost center after settlement in FAGLL03 REPORT

we have process of material issue thru maintennce order. after issuing material FI entry is on respective gl and maintence order
in report fagll03 we can see this combination and then after settlement of cost of order on cost center we are not able to see cost center in report fagll03.
is it possible to get cost center after settlement in this report.
if no then how can we see cost center / gl / material report for maintence orders.

You can't able to see the cost center report until settle the maintenance order to cost center with secondary cost element.
after settlement also you can't see in FAGLL03, you can see only cost center report with secundry cost element

User Exit for maintaining Checking Rule while creating Sales Order

Hi Gurus,
I have a requirement where I need to assign a particular value to Checking Rule (VA02 -> Display Availability Button -> Checking Rule field (beside Checking Group field)) while creating a Sales Order in SD (via. IDOC's).
In my requirement, within one Checking Group there are multiple checking rules assigned. When I am trying to assign the checking group in userexit_move_field_to_vbap (include MV45AFZZ), it is picking up the default checking rule ('A') and not the customized one defined for our requirement.
Is there any other user exit within which I can directly assign the Checking Group and Checking Rule while creating the sales order, please suggest.
Regards,
Arvind.

You can use userexit 'USEREXIT_MOVE_FIELD_TO_VBAP' in include MV45AFZZ. This is executed every time a user changes anything on a material (e.g. put in a material number) and hits return. Just raise your pop-up window there if the user puts in the particular material you are talking about. The material number is available in xvbap-matnr.
Hope that helps,
Michael

Badi for IW31 to keep check on Funds Center and Settlement rule

Hi,
My requirement is that While running IW31,if the first four characters of Settlement Rule(Cost Center) and FundsCenter is not equal to Planning Plant then an error message should be raised . Can you suggest any appropriate BADI or User Exit for this?
Path for Funds Center-->Go to>Assignment--->Funds Management
Thanks
K Srinivas

Hii Srinivas,
Did you find any solution for this, i am also encountering the same problem.
Regards,
meenakshi

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

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.

Settlement rule not created automatically

HI All,
Every time when i create a maintenance order , system did not create settlement rule automatically , when i click on settlement rule it ask with default or without default and cancel , when i click on with default the only settlement rule generated , please tell where is the gap , it should come automatically
Thanks in advance
Armaan

Hi You can not create automatically at creation, Please check the following IMG setting to make it mandatory at some point so that system will generate it automatically.
Plant Maintenance and Customer Service>Maintenance and Service Processing>Maintenance and Service Orders> Functions and Settings for Order Types> Settlement Rule: Define Time and Creation of Distribution Rule
Other wise try User Exit IWO10027
Thanks,
SS

Cost center screen layout rules

Hi All,
          In the cost center master data field cost center catagory and person responsible is mandatory i would like to make it optional can anyone advice how to do.
         thanks in advance.
regards,
Pranav

Hello
You can maintain master data for cost centers, cost elements, activity
     types, and business processes with time dependencies. You can make
     changes at any time for any given time interval. Data storage also takes
     place with a time reference. In this way, a master data record can have
     multiple database records storing different information.
     The smallest interval is one day. To ensure data consistency, you cannot
     change each field daily. The timeframes in which you can change a field
     depend on the field functions, which are fixed by the system and cannot
     be changed. Master data maintenance includes an automatic check for each
     field's time-based consistency, resulting in individual time-based
     maintenance for each field.
     The following dependencies are supported:
     o   Not time-based
     o   Day-based
     o   Period-based
     o   (Fiscal) year-based
     This function provides an overview of the time dependencies of
     individual master data fields during master data maintenance, along with
     checks and storage of consistency timeframes. You find this information
     in the "Time dependency" column.
     If you use fields requiring characteristics greater than one day and
     which are changed for the system lifetime of the object, the system
     automatically creates a new database record for this processing
     interval, and changes the time-based validity of existing records. The
     change is logged in the master data record with the time reference.
     However, a great number of changes in multiple timeframes will result in
     a correspondingly great number of data records.
     Fields which you can change freely (indicated in the DAY column) can
     possess different time dependencies only if you mark them additionally
     as historically relevant. This activates the time-based updating for the
     records.
Example
     Object 1000 has one master data record created with a fiscal year of 12
     periods and the cost center name AAAAAAAAAA. During master data
     maintenance, you change the cost center name in period 5 to BBBBBBBBBB.
     The system reacts with one of two options.
     o   "Name" is marked as historically relevant. The existing master data
         record for periods 1 - 12 must now become three records:
         1000   01-04   AAAAAAAAAA
         1000   05      BBBBBBBBBB
         1000   06-12   AAAAAAAAAA
     o   "Name" is not marked as historically relevant. The existing master
         data record remains intact, with the name changed for the entire
         existence of the record:
         1000   01-12   BBBBBBBBBB
Reg
*assign points if useful

Rule while creating Infocube

What is the rule involved while creating a Infocube?

Actually theres no rule as such involved when u create an infocube..it all depends on the type of infocube u are creating
1. standard (used for staging)
2. Real time (transactional)
1. You need to create an infocube
2. create the dimensions
3. See to it that the infocube contains atleast one key figure
4. create a datasource...select the transaction data
5. Create infopackage
6. Create transformation
7. Create DTP.
assign some points if this answer is of some help to u
Edited by: Denella D'souza on Jan 30, 2008 10:37 AM

G/L in Settlement Rule

Hi All,
How does system picks the relevant G/L code & Cost Center in settlement rule,even though in OKB9 i have not assigned them.
What is the logic behind it.
Do revert.
Regards,

Hi
The following is the order of Checks used by the system sequentially:
CHECK 1: Master Data - System will check the master data of the object (GL Account in this case) If it finds an account
assignment then it uses this one. If not then CHECK 2...
CHECK 2: OKB9 - System will check for Default account assignments here
if they are not maintained then CHECK 3....
CHECK 3: OKC9 - Substitutions - System will check if a substitution is setup to provide the account assignment. If not then
CHECK 4....
CHECK 4: MOD from Note: 483340.. This helps you to specify a CO object in the settlement rule itsellf along with GL Account
br, Ajay M

Cost center not appearing while settling to GL Account using AIAB

Hi
There is one AuC 100000019. There are two values: Rs.10000 and Rs.145500
Now i want to settle it to GL account using AIAB.
In AIAB under Category field, i gave GL (i.e. GL account as Category). Then i mentioned GL Account as settlement receiver. Then i double clicked on the settlement rule line and specified cost center (same as assets)
While settling using TCOde AIBU, it gave error, and asked for CO object. I do not know why its not picking cost center even though i specifically gave the cost center.
Please let me know what can be done
Thnx
Deepak

Hi Deepak,
What was the resolution here? I know the implementing Note 744194 does not fix this issue. I am thinking 2 possible scenarios:
1. If the cost center for AuC settlement to GL is going to be the same each time, then a GL account can be specifically setup for the purpose of this settlement and the Cost Center can be defaulted via OKB9.
2. If the Cost Center differs, then as you mentioned: It cannot be defaulted.
I am encountering the same issue, please share anything that you can.
Thank you,
Yhuss

Changing the receiver cat in the settlement rule of Product cost collector

Hi,
I have created a Product cost collector using the Transaction - KKF6N. and observed that the settlement rule got created automatically with the CAT - MAT. I need help for below queries.
1. Is it possible to change the settlement rule for the Product cost collector?
2. If yes, Could you please let me know the procedure to do this?
3. If no, what is the alternate as I want to change the CAT from MAT to ORD.
Your help is very much appreciable and Thanks in advance for the help.

Hi,
Check in order type, Which settlement profile is maintained. Then Goto settlement profile maintain receive type which you want to settle.
Regards,
Sreekanth

Validate cost center in settlement rule while creating WO in IW31

Similar Messages

Maybe you are looking for