Settlement Rule mandatory in Process order
hai,
How can I make the Settlement Rule mandatory while releasing a Process Order?
Sonali
In OKO7, select process order and in details, make the option for "ORDER- settlement required"...
karthick
Similar Messages
-
How to Make Settlement Rule Mandatory in Sales Order(In Acct Assigt Tab)
Hi Gurus,
I have a business requirement. For Free of charge 3rd party orders (yes they have FOC orders delivered by third party) the business wants to ensure that the Settlement rule should be mandatory. They enter cost center & receiver in the settlement rule.
i.e the order should not save till Settlement rule is maintained in the line item in the Acct Assignment tab.
Please let me know how this can be done.
1: Applied my brains on incompletion procedure but does not seems like it can be done there.
2: Is there something in CO where some setting can make it mandatory to enter settlement rule in Sales order?
3: I s there any other way in user-exits or ABAP?
4: Is there any setting in Item category(I could not locate any)?
5: Can this be done via Requirement class.
Please assist to resolve this one.Dear,
It depends on settings in Requirement Class (OVZG) and Account Assignment Catg (AAC) in OME9
If your AAC is E in Req Class, then your sales order is a CO object.
Requirement Class in IMG can be checked - IMG > Controling > Prod Cost Planning > Cost Obj Controling > Prod Cost By Sales Order > Control of Requirement.
Or any filed any you can Make mandatory through Transaction variant SHD0. -
Settlement rule in rework process order
Hello
When creating a rework process order without material in CORO the system is asking automatically for the settlement rules. Here we can then maintain a cost center order order. This is very nice and perfectly fine to us.
When now creating in a different case a rework order with material in COR1 (because we plan a goods receipt) the system is automatically taking the material as default settlement rule without asking the user. Would anybody know a way how to customize the system to ask the user in any case for the settlement rules? So the user really has to make a choice and is not always forgetting to update the correct values which are not only the material. (kind of a training issue but maybe the system can do something about that..)
ThanksHi,
Please click this link
http://help.sap.com/saphelp_470/helpdata/en/38/0cf817ed9b11d29fa2080009b0db33/content.htm
Rework order
thanks
krishna -
How can I make settlement rule mandatory in create work order (IW31)
How can I make settlement rule mandatory in create workorder and saving without release.
I kanow we can make settlement rule mandatory upon Release order but here requirement is
Create work order (IW21) save without releasing that time settlement rule should default.Hi,
1.If you want the settlement rule default then maintain account assignment data in technical object and when MO is created on that it would be copied into the settlement rule...
2. If you want to make those fields mandatory .... plz check up field selections in config , if you cannot find those then use SHD0 Transaction variant to make those fields mandatory.
3. Enter SHD0 , Enter IW31 in transaction and ZIW31 for transaction variant ..click create option and this takes you to IW31 initial screen , here enter required values of technical object etc and press enter and this gives you IW31 Initial scree screen variant , click continue and this takes you to inside screen and here enter required field values and on pressing enter gives you screen variant .. so you need to enter field values and check the flow of screen variants and on getting settlement rule screen variant select required option for the fields you need.
4. Finally you can save that in package created in SE80 for transporting to other client .., you can activate the variant in SHD0 -->Standard variants -->you can find activate option ..
regrds
pushpa -
Settlement rule mandatory before release of Produciton order
Dear PP Gurus,
Will you please inform me the way to configure settlement rule mandatory field before releasing the production order with out material.
Thanks in advance,
HTHi Hareesh
Go to IMG - Controlling - Product cost controlling - cost object controlling - product cost by order - period end closing - settlement - create settlement rule.
in this select the appropriate settlement rule that u assigned to ur production order type.
In this, in the block "Valid Receivers" for order , select "2 settlement required".
If this is done, when u create a production order, it will ask for the settlement rule to be defined.
Hope this is helpful to u. If so please reward points.
Chandra -
Settlement rule Mandatory for Plant Maintenance order
Hi Expert!
I want to make the option Settlement rule mandatory while creating plant maintenance order. I would really appreciate if you provide me the menu path in customisation to make this mandatory.
Thanks
JHi Jean
I do not think you can make it mandatory while creation itself.
But, you can make it mandatory (Check Functions for setting order types->settlement rule....) for order release.
Best regards
Ramki -
User Exit for the Settle rule of a Production Order
Hello all
i got a requirement to change the settlement rule of a production order to multiple receivers.
suppose i have the following rule
Categeory | Settlement Reciever | Receiver Short text | % | Settlement Type | No | Source Assignment
MAT ZMDT89 ZMDT88 100 FUL 1 left as blank
now my requirement is that i have to default the source assignment as 200 (Materials) so as to allow the other reciever entered with the same settlement type as FUL and also the No should be 2
i.e. my req is like this
Categeory | Settlement Reciever | Receiver Short text | % | Settlement Type | No | Source Assignment
MAT ZMDT89 ZMDT88 100 FUL 1 200
G/L G/L A/C no G/L shor text 100 FUL 2 100
the bold one is i have to ADD
the T-Code is CO02.
your help is highly appreciated...
thanks in advancehi,
check these exits in co02.
Transaction Code - CO02 Change Production Order
Enhancement/ Business Add-in Description
Enhancement
PPCO0010 Enhancement in make-to-order production - Unit of measure
PPCO0012 Production Order: Display/Change Order Header Data
PPCO0013 Change priorities of selection crit. for batch determination
PPCO0015 Additional check for document links from BOMs
PPCO0016 Additional check for document links from master data
PPCO0017 Additional check for online processing of document links
PPCO0018 Check for changes to production order header
PPCO0019 Checks for changes to order operations
PPCO0021 Release Control for Automatic Batch Determination
PPCO0022 Determination of Production Memo
PPCO0023 Checks Changes to Order Components
STATTEXT Modification exit for formatting status text lines
PPCO0009 Enhancement in goods movements for prod. process order
CCOWB001 Customer exit for modifying menu entries
COIB0001 Customer Exit for As-Built Assignment Tool
COZF0001 Change purchase req. for externally processed operation
COZF0002 Change purchase req. for externally procured component
PPCO0001 Application development: PP orders
PPCO0002 Check exit for setting delete mark / deletion indicator
PPCO0003 Check exit for order changes from sales order
PPCO0004 Sort and processing exit: Mass processing orders
PPCO0005 Storage location/backflushing when order is created
PPCO0006 Enhancement to specify defaults for fields in order header
PPCO0007 Exit when saving production order
PPCO0008 Enhancement in the adding and changing of components
reward points if hlpful. -
Problem in maintaining the settlement rule in the maintenance order
Dear Friends,
I have a problem ,When I am trying to maintain the settlement rule in the maintenance order ,I am getting information like below
Decentralized system -> note settlement rule is not distributed
Message no. /ISDFPS/PM124
Diagnosis
You navigated to the settlement rule.
System Response
The system informs you that a settlement rule can be created but that it will not be distributed to the target system. Settlement is carried out in the target system, where the order is usually settled to the WBS element of the operation.
Can anyone throw some light on how this is happeing and remedy?
Appreciating your early responseHello
Please check
TC --> KSR2_ORC
Please maintain the Strategy Sequences for Automatic Generation of Settlement Rule.
You define a strategy sequence for automatic generation of settlement rules for internal orders.
Regards,
Rakesh
Edited by: RAKESH ASHOK MANE on Sep 3, 2010 12:37 PM -
Report on settlement profile/rule for the Process Orders ?
Is there any report which will display settlement profile for process order or settlement rule for process order.
Hi,
Did you try this one: KOSRLIST_OR - Settlement Rules?
Regards,
Eli -
Maintenance Order Settlement Rule Mandatory
Dear Masters,
I want to make the settlement rule to be mandatory at the time of releasing a maintenance order,can anybody tell me how to achieve this?
Hope for a sooner reply. Thanks in advance.
Chin2Hey Shailendra,
Thanks for your reply, your answer solved my question.
Thanks a lot once again
Chin2 -
No access to settl rule when copying Sales order from Quotation
Hi all
Can you help me on my following issue :
I create quotation in which I refer to a settlement rule.
WHen creating a sales order in reference to my quotation, the settlement rule in the "item account assignment" tab is not reachable ...
This mean that all costs are posted on the quotation but not in the sales order.
But we would like to keep all costs on the sales order, as we do in all our process.
I've checked the copying rules but found nothing..
Any suggestions?
thanks in advance
martineIn the standard sales order screen (type OR for example) if you go to Go To Item Account Assignment you can press on the button"Settlement Rule "
But when copying Sales Information to Sales order with standard copying requirements, you can not presse on the button "settlement rule"
Furthermore, in this tab, a field called "PC DUMMY" is now appaered on the screen ...??!!!
Any idea of what to do ??
thanks !
martine -
Default Settlement Rule of PM Maintenance Order
Hi,
While creation of settlement rule on Maintenance Order, Option appears of default settlement rule. Whenever i select that option on Settlement Rule definition screen, two rows appears for the same Cost reciever automatically ( One for Full settlement and second for Periodical Settlement) But i only want Full settlement option to appear on screen in this scenario. Can anybody pin point the root cause and share the solution of it.hi
while defining the settlement profile specify CTR as default settlement receiver and check ,and also make the settlement profile mandatory for order release,
regards
thyagarajan -
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
bobbyHi,
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 SDI in prod order
Hi,
I used strategy make to order in my client, when i create prod order the settlement rule is always MAT and want the settlement rule to be SDI to my sales order.
What should i config to achieve this ? since i tried to change order type dependent parameter and it did not allow (only PP1 and PP2 allowed).
Please kindly help
Best regards,
Freddy HaHi,
i tried to change the requirement class for makte to order so the setlement become SD1 in setting for requirement type KE. In the OPJH i still used PP01. and now it work thanx for all off your input.
Thankx once again.
Good day,
Freddy Ha -
Doubt about the settlement rule of the Production ORder
The only default distribution rule allowed for a PP order is PP1 or PP2. We would need to change that to allow settlement to multiple receivers as a default. If that is the case, we may want to look into a user exit to update the settlement rule during production order creation instead so that the G/L account is correct from the beginning.
Currently when we create the production order, the settlement rule will default the below, I am not sure if a user exit is able to maintain the Source as 200 (Materials)?
If yes, we can then add the second rule for Source 100 (Labor and Mfg) via the user exit as well.
In this case, SAP will not prompt us error of settlement with 200%, as they are from difference Sources.
now anybody can explain me about the User EXit we have to correct thisany help on this.. please its very urgent
thanks in advance
Maybe you are looking for
-
How do I turn off OS notifications in upper right corner
How do I turn off the little banner notifications for system updates, it's driving me insane, it pops out every five minutes. In Notifications in System Preferences there is nothing there for the OS, only various specific applications. Thank you.
-
I need to export an uncompressed QT at 2048 x 1152 is this possible?
the post house I'm using sent a QT at 2048x1152 with component Y'CbCr . Importing the file seemed to leave it in tact but I can't figure out how to export at the same resolution.
-
Re: Wireless printing stops working with Home Hub ...
I have had to fix a few clients home networks and was perturbed to find there is a pattern between the new home hubs and existing wireless printers. I too found no logical reason why the connection would drop or go twilight zone. I searched after fix
-
All, Issue 1 I am looking to view a BOBJ Webi Reports, Xcelsius Dashboards based on BI service and BW connection within the Portal iView, Based on the documentation available I have not been able to create a URL, KM Navigational or find a standard Xc
-
Oracle-validated generates strange user id 54321 for oracle
Hi! When installing OEL 5.5 x86_64 on both physical and virtual servers, using both kickstart and manual installation, I have noticed following thing oracle user id is 54321 as opposed to "standart" user id 500. Is this expected behaviour or do I hav