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.

Similar Messages

How to make all fields mandatory in sales order T- code VA01 initial screen

Dear all,
how to make all fields mandatory in sales order T- code VA01 initial screen itself
The fields are
Sales Organization
Distribution Channel
Division
Sales Office
Sales Group
Regards,
Amar Reddy

Hi,
You can use Transaction Variant to achieve this functionality.Please go through the following link which helps you in creating the same.
[Link|http://wiki.sdn.sap.com/wiki/display/Snippets/TransactionVariant-AStepbyStepGuidefor+Creation]
Regards,
Phani Prasad

How to make Settl. rule mandatory before release ?

Hi,
I have project with settlement to AUC and to the superior wbs elements. I want to have the settlement rule to be made mandatory (before Release) for all those WBS elements, where it will be settled to superior WBS elements. How to make this mandatory ? Is it possible through validations or is there any BAdI available for this ? I had checked for user exits, i could not find any suitable one.
thanks in advance.
Vinodh

Hi
1.For making settlement rule manditory, check with function module "CJPN_SETTLEMENT_RULES" and put into validation in OPSI t.code..
2. when settlement rule is created system status will be set to SETC. So while saving the project , you can check if the status is SETC or not and the throw the required error.
You can use BAdi = Workorder_update interface AT_SAVE.
For staus check you can use BAPI_STATUS_CHECK and pass Objnr of the WBS and check for SETC ( Sys Status = I0028).
try this options
Thanks
S.Murali

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

How to make the status of a sales order complete of which PART DELIVERY

How to make the status of a sales order complete of which PARTIAL DELIVERY has already done. <b>(Assigning rejection status not accepted)</b>

Hi Gyana
There is no document with me. But I can confidently say that because I am using this functionality.
In my case I have created a Order Reason as "Short Closed". once you short close this order only the balance quantity gets rejected (provided you have already made previous delivery and PGI).
Try it in one of your test clients if you have. Once it is short Closed it wont also show in the orders due for processing in Production.
Also you can generate reports based on this if your customer wants to know how many order he has short closed, qty of item short closed etc.
Try it.
Rgds
Sunil

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

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

How to make the connection between a sale order and an invoice in SDK

Hi,
Im trying to make the connection between a sales order and an invoice using the SDK.
Here is how i create each of them:
Invoice:
public int SalesInvoiceInternalSave(string buisnesspartnerCardCode, DateTime dueDate, double discountPercent, string id, IList<InternalItem> items, ref int invoiceId)
      int res = 0;
      SAPbobsCOM.Documents invoice_entry = (SAPbobsCOM.Documents)Company.GetBusinessObject(SAPbobsCOM.BoObjectTypes.oInvoices);
      invoice_entry.CardCode = buisnesspartnerCardCode;
      invoice_entry.DocDueDate = dueDate;
      invoice_entry.DiscountPercent = discountPercent;
      invoice_entry.Reference2 = id;
      foreach (InternalItem item in items)
        invoice_entry.Lines.WarehouseCode = item.Shopid;
        invoice_entry.Lines.ItemCode = item.Code;
        invoice_entry.Lines.ItemDescription = item.Name;
        invoice_entry.Lines.Quantity = item.Quantity;
        invoice_entry.Lines.UnitPrice = item.Price;
        invoice_entry.Lines.Add();
      res = invoice_entry.Add();
      return res;
Sales order:
    public Boolean SalesOrderInternalSave(string orderId, string buisnesspartnerCardCode, DateTime dueDate, IList<InternalItem> items)
      SAPbobsCOM.Documents order_entry = (SAPbobsCOM.Documents)Company.GetBusinessObject(SAPbobsCOM.BoObjectTypes.oOrders);
      order_entry.CardCode = buisnesspartnerCardCode;
      order_entry.DocDueDate = dueDate;
      foreach (InternalItem item in items)
        order_entry.Lines.WarehouseCode = item.Shopid;
        order_entry.Lines.ItemCode = item.Code;
        order_entry.Lines.ItemDescription = item.Name;
        order_entry.Lines.Quantity = item.Quantity;
        order_entry.Lines.UnitPrice = item.Price;
        order_entry.Lines.Add();
      int res = order_entry.Add();
      return res == 0;
What do i need to change to get the connection between the two of them?
And how do you insert a amount (not percent) discount into an invoice?
Regards,
Torben

Hi,
Add the sale order, then add the invoice. and while adding the invoice please add the following details to the invoce documen
invoice_entry.Lines.BaseEntry = 'Doc entry of the newly created SO
invoice_entry.Lines.BaseLine = 'Line No of the SO
invoice_entry.Lines.BaseType = 17 'For sales order document type.
Hope it helps,
Vasu Natari.

How to make the line items of sales order cannot be deleted.

Hi All,
Is there any Enhancement spots or user-exits which make the line items of sales order cannot be deleted if item category is 'TAN'.
Thanks in Advance,
Sudhakar Reddy .A

Hi All,
If you doesn't want to delete sales order line items then we have write in the Include Program which has mentioned below and in the form .....endform.
Program Name : Include MV45AFZB
_Example:_
form userexit_check_xvbap_for_delet using us_error
us_exit.
IF .......
US_EXIT = CHARX.
ENDIF.
endform.

HOW TO MAKE MATERIAL DESCRIPTION FIELD IN SALES ORDER AS UNEDITABLE

how to make the material description field as un editable in sales order , pls help me

Through Transaction Variant <b>SHD0</b>
Refer the thread
/message/4083386#4083386 [original link is broken]
Message was edited by:
SHESAGIRI.G

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
martine

In 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

How to make payment mean available in Sales Order?

Hi,
Customer is using 2007A PL30 Australia/New Zealand localization. We found in US Demo database, payment mean is available in Sales Order. Business nature of this customer involves down payment/deposit/refund/cancel deposit. We think of using payment mean rather than down payment invoice because of its limitation. May I know where to make this setup or it is due to localization?
Regards
Thomas

Hi,
It could be probably caused by business process nature issue. To know more detail, download this file from partner portal : SAP Business One Globalization Knowledge Base.
Rgds,

Price mandatory in sales order

Hi SAP Experts,
I want to make price ( PR00) mandatory in sales order . The sales order should not be allowed to save with out the price. How do I achieve this? I have made the following setting.
1. Made PR00 mandatory in pricing procedure.
2. Assigned an incompletion log at the item level with screen PKON and status 06
but I still can save my sales order.
Kindly help
Beena

Hi Beena,
You have done it right by making the Condition Type PR00 as Mandatory in the Pricing Procedure and also using the Item Condition PKON in the Incompletion log.
All you need to do is in the same Incompletion log mark the field as WARNING.
Hope this works for you.
REWARD if it helps you!!
Regards,
Ajinkya

Quotations as mandatory for sales order creation

Dear SD experts
We have a situation where the user from one of our sales organization wants to make Quotations as mandatory for sales order creation. Means that no order will be created unless it has a refrence to a quotation.
But the problem is that this sales order type u201CZordu201D is being used by multiple sales organizations. Hence making quotations mandatory in the order type will even activate mandatory check on other companies using this order type.
Is there a way to make the quotations mandatory on sales organization or user based role? Or any other way. Please advise.
Best regards,

Hi
Say example sales org 1000 where you need to create sales orders with mandatory reference to quotation
Have a order type ZOR with mandatory reference marked inits configuration in VOV8
Then in T code OVAZ configuartion configuration you can restrict ZOR order type to be used only for sales areas which has 1000 has sales orgs
For other sales orgs sales areas dont maintain ZOR in the allowed order types
Regards
Raja

How to make a field profit center mandatory in sales order?

Dear GURUS,
Please help in getting answer for following question.
How to make a field profit center mandatory in sales order?
With Regards
Sandeep D.

Hi,
There are 2 ways to make profit center mandatory
1.Transaction Variant
2.Incompletion procedure
1.Transaction Variant
Step 1:Goto Tcode shd0 and input transaction as va01 and give name of transaction variant as ( example. zva01 ) and click on create or F5
Step 2.Then it takes you to sales order screen.Just click on enter untill you see profit center field.
Step 3.check the box required against profit center.
Step 4.click on save ( under a package name or as local object ) and exit
Step 5.Assign transaction variant to your sales order type through tcode v0v8.
2.Incompletion Procedure
You can add the field table-vbap,field- prctr,status-04,check-warning to your existing incompletion procedure Tcode- ova2 assigned to your order type in tcode vov8 and check the box - incomplete messeges for your order type through tcode vov8.
If incompletion procedure is not assigned to your order type than you have to create a new incompletion procedure and assign it to order type.

How to Make Settlement Rule Mandatory in Sales Order(In Acct Assigt Tab)

Similar Messages

Maybe you are looking for