CRMD_ORDERADM_H - Business Transaction header table

In the table CRMD_ORDERADM_H there is a field Posting Date.  Is this a generated field or a field that a user enters and can this value be changed? Thanks

Hi,
This field is a generated field, its the system date when the order is created by the user.
It cannot be changed.
Regards,
PePe

Similar Messages

  • Enhance Business Transaction with table

    Hi,
    I have to enhance a Business Transaction (Sales Contract) with a table, but I can´t see this option nor EEWB or AET. I can add fields in both tools, and I can also add a table, but only for BUPA, not in Business Transaction. This table for add is going to be viewed in WebUI.
    What can be done?. Thank you in advance for your help.
    Regards,

    HI,
    You can create this using AET table. Fiest open your Sales Contract Document then click Configuration butoon you have to choose which area to configure afetr that you will get popup in that click enhanced fields there you can see
    Regards,
    Deepika.

  • Controlling Business transaction field in COSS and COSP table

    Hi all,
    I am trying to understand the idea of the field business transaction in tables COSS and COSP (where as much as I understood are the line items in CO - please corect me if I am wrong). It seems logically that this field is connected somehow to the SAP transactions. Do you know where is this connection and how can I see it?
    I need to know which SAP transactions will get business transaction COIN for example. If you have some documentaion or explanation of how this works, it will be very useful to me.
    Thank you,
    Maria

    Hi Maria,
    When you run settlement for internal orders using KO88, the records are saved into COSS table with the Business transaction KOAO.
    Just for your understanding the meaning of the main CO tables:
    - COEP: this is the CO document line items table (the one that is searched when you run, for example, KSB1 or KOB1 report transactions);
    - COSS: this is the CO cost totals table for internal postings, that is, the postings done into CO module that is going to reflect on the same CO module;
    - COSP: this is the CO cost totals table for external postings, that is, the postings done into any module that is going to reflect on CO module.
    To complete what it had been explained: COIN means the postings done from any module to CO.
    I hope it helps you.
    Best Regards,
    Daniel

  • Link between business transactions in CRMD_ORDERADM_H

    Hi,
    Could you please help me with a table/tables that contains link between different business transactions.
    For example, if I need purchase order associated with an invoice?
    I know that CRMD_ORDERADM_H contains information regarding both purchase order and invoice.
    I can use Transaction Code bbp_pd, however, I need the underlying tables.
    I will use this information to pull data from SRM to BW.
    Thanks,

    Hi,
    Instead of using SELECT statements,you cna use standard Function modules to fetch the required data.
    e.g.To get all the details for a PO,you can use the FM "BBP_PD_PO_GETDETAIL".
    In the export parameter,table "E_HEADER_REL",you can see the follow on documents details for the PO.
    Hope this helps.
    BR,
    Disha.

  • Business Transactions:  CRMD_ORDERADM_H

    I wanted to check whether the table CRMD_ORDERADM_H will also store the opportunity headers. 
    For example if I have an opportunity which is in the table CRMD_OPPORT_H can I find this same opportunity in CRMD_ORDERADM_H if I search for it and also will CRMD_OPPORT_H-GUID be the same as CRMD_ORDERADM_H-GUID
    Thanks

    Yes, because of one order model,  you can see in both tables. All the business transactions will be be stored in CRMD_ORDERADM_H.

  • Master table for "Business Transaction"

    Dear all,
    Do you where can i get a list of "Business transaction" MLHD-GLVOR?
    FYI, this is MM related "Business transaction".
    Please comment.
    Thanks in advance.

    Hi,
    CRMD_ORDERADM_H Contains the Header Information for a Business Transaction.
    link:[http://forum.saptechies.com/viewtopic.php?t=3349]
    search in this link.
    check this hope it'll help.
    Regards,
    Sneha.

  • Error : Transaction header and line tables cannot be empty

    please can some one help me.
    when i want to create an invoice without anuy line, i have the error : Transaction header and line tables cannot be empty .
    can some one tell me how can i solve this
    regards.

    Hi,
    I really don't know if it is possible to create an invoice in AR with no transaction lines. When I interface invoices from another system to AR (and there is no need to detail inventory items), I use a single line with a dummy inventory item or with no inventory item (inventory_item_id and warehouse_id set to null) in transaction lines, and I use the description field to describe the link to the other software in a user-friendly way.
    Regards,
    Ketter Ohnes
    Message was edited by:
    Ketter Ohnes

  • Header table for service contract like CRMD_DHR_HEADOPP

    Hi,
    As we can get all the details from CRMD_ORDERADM_H and CRMD_ORDERADM_I,  table for the business transactions, along with this for the opportunity and lead we also have the header table as CRMD_DHR_HEADOPP and CRMD_DHR_LEAD, from which we can directly select the prospect and employee responsible. Now we are working with Service/Sales quotation and  contract, for this Is there any header level table from where we can get the details for prospect and employee responsible.without using the CCRMD_ORDER_INDEX table.
    Regards,
    Zafar

    Hello Zafar,
    I such cases I use the BOL-model to get the data. To find out your relevant BOL-entities go to the right WebUI screen and press F2. Then you see the application, view and context node and you can find out which BOL-entity you need.
    Best regards,
    Thomas Wagner

  • Short dump "Time limit exceeded" when searching for Business Transactions

    Hello Experts,
    We migrated from SAP CRM 5.2 to SAP CRM 7.0. After migration, our business transaction search (quotation, sales order, service order, contract etc) ends with the short dump "Time limit exceeded" in class CL_CRM_REPORT_ACC_DYNAMIC, method DATABASE_ACCESS. The select query is triggered from line 5 of this method.
    Number of Records:
    CRMD_ORDERADM_H: 5,115,675
    CRMD_ORDER_INDEX: 74,615,914
    We have done these so far, but the performance is still either poor or times out.
    1. DB team checked the ORACLE parameters and confirmed they are fine. They also checked the health of indices in table CRMD_ORDER_INDEX and indices are healthy
    2. Created additional indices on CRMD_ORDERADM_H and CRMD_ORDER_INDEX. After the creation of indices, some of the searches(without any criteria) work. But it takes more than a minute to fetch 1 or 2 records
    3. An ST05 trace confirmed that the selection on CRMD_ORDER_INDEX takes the most time. It takes about 103 seconds to fetch 2 records (max hits + 1)
    4. If we specify search parameters, say for example a date or status, then again we get a short dump with the message "Time limit exceeded".
    5. Observed that only if a matching index is available for the WHERE clause, the results are returned (albeit slowly). In the absence of an index, we get the dump.
    6. Searched for notes and there are no notes that could help us.
    Any idea what is causing this issue and what we can do to resolve this?
    Regards,
    Bala

    Hi Michael,
    Thanks. Yes we considered the note 1527039. None of the three scenarios mentioned in the note helped us. But we ran CRM_INDEX_REBUILD to check if the table CRMD_ORDER_INDEX had a problem. That did not help us either.
    The business users told us that they mostly search using the date fields or Object ID. We did not have any problem with search by Object ID. So we created additional indices to support search using the date fields.
    Regards,
    Bala

  • Report Painter- Restricting Business Transactions

    Hi,
    I'm creating a report using report painter & would like to prevent Actual Overhead Distribution data (business transaction RKIV) from being reflected in this report. I can add business transactions in the report through Edit -> General Selection data. How do I block a particular business transaction in this report ?
    Regards,
    Sangeeta

    Hi Sanjeeta,
    there's several ways to do this:
    (1) On the report characteristics window, enter range of values limited the values you want. To add more range, click on the more button, and keep restricting until you have what you want. Then select "no explode".
    (2) My recommended way to do it is to create a basic SET via GS01. Table = GLPCT, Field=ACTIV.
    On the set header, Select "Suppress". Enter the values that you want included, and leave out the excluded values. You can use range of course!
    Then back on the report characteristic screen, enter you SET name and check the flag for entering sets. Select "no explode". With this option, if you ever need to change your Business transaction values, just change the SET and the report will query the updated values.
    If you use a report variant to carry out the same solution, just note that everytime you need to change the values, you have to change the variant, transport, and regenerate the report (assuming that you do not change enterprise level variants directly in production)
    Hope this helps,
    Sam

  • Business transaction key in account determination..?

    Hi all
    Can anybody explain me in simple form form, what is business transaction key in account determination , for eg, GBB,BSA,BSX,PRD,VBR,.WRX....etc (Approximately 60 transaction keys in std SAP)
    If i want to do configuration the for new client, what are all the business transaction key,,, How the configuration wil happen..?
    Pls giv me expaination,
    Reply will be rewardable..
    Thanks
    sap-mm

    Hi MM,
    Please Search in SDN threads solution is given already in lot of threads.
    Go to SAP Library
    SPRO> Help> SAP Library
    Or go to SPRO> IMG> MM>Valuation and Account Assignment>Account determination> Account det without wizard> configure Automatic postings
    Click on IMG ACTIVITY DOCUMENTATION
    These transactions are important for Accounts.
    Postings are made to G/L accounts automatically in the case of Invoice Verification and Inventory Management transactions relevant to Financial and Cost Accounting.
    Example:
    Posting lines are created in the following accounts in the case of a goods issue for a cost center:
    Stock account
    Consumption account
    Agency business: income (AG1)
    This transaction can be used in agency business for income deriving from commission (e.g. del credere commission). The account key is used in the calculation schemas for agency business to determine the associated revenue accounts.
    Agency business: turnover (AG2)
    This transaction can be used in agency business if turnover (business volume) postings are activated in Customizing for the payment types. The account key is specified in Customizing for the billing type.
    Agency business: expense (AG3)
    This transaction can be used in agency business for commission expenses. The account key is used in the calculation schemas for agency business to determine the associated expense accounts.
    Expense/revenue from consumption of consignment material (AKO)
    This transaction is used in Inventory Management in the case of withdrawals from consignment stock or when consignment stock is transferred to own stock if the material is subject to standard price control and the consignment price differs from the standard price.
    Expenditure/income from transfer posting (AUM)
    This transaction is used for transfer postings from one material to another if the complete value of the issuing material cannot be posted to the value of the receiving material. This applies both to materials with standard price control and to materials with moving average price control. Price differences can arise for materials with moving average price if stock levels are negative and the stock value becomes unrealistic as a result of the posting. Transaction AUM can be used irrespective of whether the transfer posting involves a transfer between plants. The expenditure/income is added to the receiving material.
    Provisions for subsequent (end-of-period rebate) settlement (BO1)
    If you use the "subsequent settlement" function with regard to conditions (e.g. for period-end volume-based rebates), provisions for accrued income are set up when goods receipts are recorded against purchase orders if this is defined for the condition type.
    Income from subsequent settlement (BO2)
    The rebate income generated in the course of "subsequent settlement" (end-of-period rebate settlement) is posted via this transaction.
    Income from subsequent settlement after actual settlement (BO3)
    If a goods receipt occurs after settlement accounting has been effected for a rebate arrangement, no further provisions for accrued rebate income can be managed by the "subsequent settlement" facility. No postings should be made to the account normally used for such provisions. As an alternative, you can use this transaction to post provisions for accrued rebate income to a separate account in cases such as the one described.
    Supplementary entry for stock (BSD)
    This account is posted when closing entries are made for a cumulation run. This account is a supplementary account to the stock account; that is, the stock account is added to it to determine the stock value that was calculated via the cumulation. In the process, the various valuation areas (for example, commercial, tax), that are used in the balance sheet are taxed separately.
    Change in stock (BSV)
    Changes in stocks are posted in Inventory Management at the time goods receipts are recorded or subsequent adjustments made with regard to subcontract orders.
    If the account assigned here is defined as a cost element, you must specify a preliminary account assignment for the account in the table of automatic account assignment specification (Customizing for Controlling) in order to be able to post goods receipts against subcontract orders. In the standard system, cost center SC-1 is defined for this purpose.
    Stock posting (BSX)
    This transaction is used for all postings to stock accounts. Such postings are effected, for example:
    In inventory management in the case of goods receipts to own stock and goods issues from own stock
    In invoice verification, if price differences occur in connection with incoming invoices for materials valuated at moving average price and there is adequate stock coverage
    In order settlement, if the order is assigned to a material with moving average price and the actual costs at the time of settlement vary from the actual costs at the time of goods receipt
    Because this transaction is dependent on the valuation class, it is possible to manage materials with different valuation classes in separate stock accounts.
    Revaluation of other consumption (COC)
    This transaction/event key is required for the revaluation of consumption in Actual Costing/Material Ledger.
    Revaluation of consumption valuates single-level consumption using the actual prices determined in the Actual Costing/Material Ledger application. This revaluation can either take place in the account where the original postings were made, or in a header account.
    The header account is determined using the transaction/event key COC.
    Del credere (DEL)
    Transaction/event key for the payment/invoice list documents in Purchasing. The account key is needed in the calculation schema for payment/settlement processing to determine the associated revenue accounts.
    Small differences, Materials Management (DIF)
    This transaction is used in Invoice Verification if you define a tolerance for minor differences and the balance of an invoice does not exceed the tolerance.
    Purchase account(EIN), purchase offsetting account (EKG), freight purchase account (FRE)
    These transactions are used only if Purchase Account Management is active in the company code.
    Note
    Due to special legal requirements, this function was developed specially for certain countries (Belgium, Spain, Portugal, France, Italy, and Finland).
    Before you use this function, check whether you need to use it in your country.
    Freight clearing (FR1), provision for freight charges (FR2), customs duty clearing (FR3), provision for customs duty (FR4)
    These transactions are used to post delivery costs (incidental procurement costs) in the case of goods receipts against purchase orders and incoming invoices. Which transaction is used for which delivery costs depends on the condition types defined in the purchase order.
    You can also enter your own transactions for delivery costs in condition types.
    External service (FRL)
    The transaction is used for goods and invoice receipts in connection with subcontract orders.
    If the account assigned here is defined as a cost element, you must specify a preliminary account assignment for the account in the table of automatic account assignment specification (Customizing for Controlling) in order to be able to post goods receipts against subcontract orders. In the standard system, cost center SC-1 is defined for this purpose.
    External service, delivery costs (FRN)
    This transaction is used for delivery costs (incidental costs of procurement) in connection with subcontract orders.
    If the account assigned here is defined as a cost element, you must specify a preliminary account assignment for the account in the table of automatic account assignment specification (Customizing for Controlling) in order to be able to post goods receipts against subcontract orders. In the standard system, cost center SC-1 is defined for this purpose.
    Offsetting entry for stock posting (GBB)
    Offsetting entries for stock postings are used in Inventory Management. They are dependent on the account grouping to which each movement type is assigned. The following account groupings are defined in the standard system:
    Purchase order with account assignment (KBS)
    You cannot assign this transaction/event key to an account. It means that the account assignment is adopted from the purchase order and is used for the purpose of determining the posting keys for the goods receipt.
    Exchange Rate Differences Materials Management(AVR) (KDG)
    When you carry out a revaluation of single-level consumption in the material ledger for an alternative valuation run, the exchange rate difference accounts of the materials are credited with the exchange rate differences that are to be assigned to the consumption.
    Exchange rate differences in the case of open items (KDM)
    Exchange rate differences in the case of open items arise when an invoice relating to a purchase order is posted with a different exchange rate to that of the goods receipt and the material cannot be debited or credited due to standard price control or stock undercoverage/shortage.
    Differences due to exchange rate rounding, Materials Management (KDR)
    An exchange rate rounding difference can arise in the case of an invoice made out in a foreign currency. If a difference arises when the posting lines are translated into local currency (as a result of rounding), the system automatically generates a posting line for this rounding difference.
    Exchange Rate Differences from Lower Levels (KDV)
    In multi-level periodic settlement in the material ledger, some of the exchange rate differences that have been posted during the period in respect of the raw materials, semifinished products and cost centers performing the activity used in the manufacture of a semifinished or finished product are debited or credited to that semifinished or finished product.
    Consignment liabilities (KON)
    Consignment liabilities arise in the case of withdrawals from consignment stock or from a pipeline or when consignment stock is transferred to own stock.
    Depending on the settings for the posting rules for the transaction/event key KON, it is possible to work with or without account modification. If you work with account modification, the following modifications are available in the standard system:
    None for consignment liabilities
    PIP for pipeline liabilities
    Offsetting entry for price differences in cost object hierarchies (KTR)
    The contra entry for price difference postings (transaction PRK) arising through settlement via material account determination is carried out with transaction KTR.
    Accruals and deferrals account (material ledger) (LKW)
    If the process of material price determination in the material ledger is not accompanied by revaluation of closing stock, the price and exchange rate differences that should actually be applied to the stock value are contra-posted to accounts with the transaction/event key LKW.
    If, on the other hand, price determination in the material ledger is accompanied by revaluation of the closing stock, the price and exchange rate differences are posted to the stock account (i.e. the stock is revalued).
    Price Difference from Exploded WIP (Lar.) (PRA)
    If you use the WIP revaluation of the material ledger, the price variances of the exploded WIP stock of an activity type or a business process are posted to the price differences account with transaction/event key PRA.
    Differences (AVR Price) (PRC)
    In the alternative valuation run in the material ledger, some of the variances that accrue interest in the cost centers, are transfer posted to the semifinished or finished product.
    Price differences (PRD)
    Price differences arise for materials valuated at standard price in the case of all movements and invoices with a value that differs from the standard price. Examples: goods receipts against purchase orders (if the PO price differs from the standard pricedardpreis), goods issues in respect of which an external amount is entered, invoices (if the invoice price differs from the PO price and the standard price).
    Price differences can also arise in the case of materials with moving average price if there is not enough stock to cover the invoiced quantity. In the case of goods movements in the negative range, the moving average price is not changed. Instead, any price differences arising are posted to a price difference account.
    Depending on the settings for the posting rules for transaction/event key PRD, it is possible to work with or without account modification. If you use account modification, the following modifications are available in the standard system:
    None for goods and invoice receipts against purchase orders
    PRF for goods receipts against production orders and
    order settlement
    PRA for goods issues and other movements
    PRU for transfer postings (price differences in the case
    of external amounts)
    Price Differences (Material Ledger, AVR) (PRG)
    When you carry out a revaluation of single-level consumption in the material ledger during the alternative valuation run, the price difference accounts of the materials are credited with the price differences that are to be assigned to the consumption.
    Price differences in cost object hierarchies (PRK)
    In cost object hierarchies, price differences occur both for the assigned materials with standard price and for the accounts of the cost object hierarchy. In the course of settlement for cost object hierarchies after settlement via material account determination, the price differences are posted via the transaction PRK.
    Price Difference from Exploded WIP (Mat.) (PRM)
    If you use the WIP revaluation of the material ledger, the price and exchange rate differences of the exploded WIP stock of a material are posted to the price difference account with transaction/event key PRM.
    Price differences, product cost collector (PRP)
    During settlement accounting with regard to a product cost collector in repetitive manufacturing, price differences are posted with the transaction PRP in the case of the valuated sales order stock.
    This transaction is currently used in the following instances only:
    Production cost collector in Release 4.0
    Product cost collector in IS Automotive Release 2.0 (product cost collector in connection with APO)
    Offsetting entry: price differences, product cost collector (PRQ)
    The offsetting (contra) entry to price difference postings (transaction PRP) in the course of settlement accounting with respect to a product cost collector in repetitive manufacturing in the case of the valuated sales order stock is carried out via transaction PRQ.
    This transaction is currently used in the following instances only:
    Production cost collector in Release 4.0
    Product cost collector in IS Automotive Release 2.0 (product cost collector in connection with APO)
    Price Differences from Lower Levels (PRV)
    In multi-level periodic settlement in the material ledger, some of the price differences posted during the period in respect of the raw materials, semifinished products, and cost centers performing the activity used in a semifinished or finished product, are transfer posted to that semifinished or finished product.
    Price differences for material ledger (PRY)
    In the course of settlement in the material ledger, price differences from the material ledger are posted with the transaction PRY.
    Expense and revenue from revaluation (retroactive pricing, RAP)
    This transaction/event key is used in Invoice Verification within the framework of the revaluation of goods and services supplied for which settlement has already taken place. Any difference amounts determined are posted to the accounts assigned to the transaction/event key RAP (retroactive pricing) as expense or revenue.
    At the time of the revaluation, the amounts determined or portions thereof) are posted neither to material stock accounts nor to price difference accounts. The full amount is always posted to the "Expense from Revaluation" or "Revenue from Revaluation" account. The offsetting (contra) entry is made to the relevant vendor account.
    Invoice reductions in Logistics Invoice Verification (RKA)
    This transaction/event key is used in Logistics Invoice Verification for the interim posting of price differences in the case of invoice reductions.
    If a vendor invoice is reduced, two accounting documents are automatically created for the invoice document. With the first accounting document, the amount invoiced is posted in the vendor line. An additional line is generated on the invoice reduction account to partially offset this amount. With the second accounting document, the invoice reduction is posted in the form of a credit memo from the vendor. The offsetting entry to the vendor line is the invoice reduction account. Hence the invoice reduction account is always balanced off by two accounting documents within one transaction.
    Provision for delivery costs (RUE)
    Provisions are created for accrued delivery costs if a condition type for provisions is entered in the purchase order. They must be cleared manually at the time of invoice verification.
    Taxes in case of transfer posting GI/GR (TXO)
    This transaction/event key is only relevant to Brazil (nota fiscal).
    Revenue/expense from revaluation (UMB)
    This transaction/event key is used both in Inventory Management and in Invoice Verification if the standard price of a material has been changed and a movement or an invoice is posted to the previous period (at the previous price).
    Expenditure/income from revaluation (UMD)
    This account is the offsetting account for the BSD account. It is posted during the closing entries for the cumulation run of the material ledger and has to be defined for the same valuation areas.
    Unplanned delivery costs (UPF)
    Unplanned delivery costs are delivery costs (incidental procurement costs) that were not planned in a purchase order (e.g. freight, customs duty). In the SAP posting transaction in Logistics Invoice Verification, instead of distributing these unplanned delivery costs among all invoice items as hitherto, you have the option of posting them to a special account. A separate tax code can be used for this account.
    Input tax, Purchasing (VST)
    Transaction/event key for tax account determination within the "subsequent settlement" facility for debit-side settlement types. The key is needed in the settlement schema for tax conditions.
    Inflation posting (WGB)
    Transaction/event key that posts inflation postings to a different account, within the handling of inflation process for the period-end closing.
    Goods issue, revaluation (inflation) (WGI)
    This transaction/event key is used if already-posted goods issues have to be revaluated following the determination of a new market price within the framework of inflation handling.
    Goods receipt, revaluation (inflation) (WGR)
    This transaction/event key is used if already-effected transfer postings have to be revaluated following the determination of a new market price within the framework of inflation handling. This transaction is used for the receiving plant, whereas transaction WGI (goods receipt, revaluation (inflation)) is used for the plant at which the goods are issued.
    WIP from Price Differences (Internal Activity) (WPA)
    When you use the WIP revaluation of the material ledger, the price variances from the actual price calculation that are to be assigned to the WIP stock, an activity type or a business process are posted to the WIP account for activities.
    WIP from Price Differences (Material) (WPM)
    When you use the WIP revaluation of the material ledger, the price and exchange rate differences that are to be assigned to the WIP stock of a material are posted to the WIP account for material.
    GR/IR clearing (WRX)
    Postings to the GR/IR clearing account occur in the case of goods and invoice receipts against purchase orders. For more on the GR/IR clearing account, refer to the SAP Library (documentation MM Material Valuation).
    Caution
    You must set the Balances in local currency only indicator for the GR/IR clearing account to enable the open items to be cleared. For more on this topic, see the field documentation.
    GR/IR clearing for material ledger (WRY)
    This transaction/event key is not used from Release 4.0 onwards.
    Prior to 4.0, it was used for postings to the GR/IR clearing account if the material ledger was active. As of Release 4.0, the transaction is no longer necessary, since postings to the GR/IR account in parallel currencies are possible.
    Reg,
    Ashok
    assign points if useful.

  • Business Transaction Screen Configuration

    How can I hide / delete extra tabs from Transaction screen....can guru's help me in this topic..
    Thanks in Advance.

    Hi,
    You can use Easy Enhancement Work Bench (EEWB).
    Easy Enhancement Work Bench - SAP’s tool enables to add custom fields to standard transactions without having to modify SAP code. In a nutshell, the way this works is that SAP allows generating custom objects in predefined containers that are linked to the various transactions.
    Transaction EEWB (Easy Enhancement work bench) is used to create the custom Fields in the Custom (new additional custom) Tab for SAP Business Objects. Thus the standard SAP CRM Transactions can be extended using the Easy Enhancement Workbench (EEWB), i.e., an extra tab is added to the View - Transaction Data in CRM Transaction.
    During the creation of the project in EEWB, a workbench as well as customizing request is defined. After the creation of project, extension(s) are created. The extension contains the information regarding the business object to be modified and the type of the extension.
    Note: In order to extend CRM’s generic business transactions, e.g. orders and opportunities, select object ‘Business Transaction’ and type ‘Add New Fields’. For business partner extensions select object ‘BUPA’, type ‘Add New Fields’.
    EEWB uses customizing include (CI) provided by SAP to make extensions easy. These customizing includes are included in the People Centric UI and relevant database tables (For instance CRMD_CUSTOMER_H and BUT000 if Business Transactions - Sales & Service Objects and Business Partner are extended respectively).
    The Z Fields added using the Transaction EEWB are appended to the table CRMD_CUSTOMER_H and the entry in the table CRMD_CUSTOMER_H  corresponds to one respective entry in the table CRMD_ORDERADM_H with HEADER_GUID.
    (Relation between two tables: CRMD_ORDERADM_H-GUID = CRMD_CUSTOMER_H-GUID.
    Reward if it helps.
    Rashit

  • Special Business Transactions

    Hello,
    What are the special business transactions that are considered in SD?
    Kindly give some examples.
    Thank you.

    Dear hk7,
    Scenarios:
    How to configure tax?
    Use the following Tcodes:
    OBQ1 --- CONDITION TABLE 
    OBQ2 --- ACCESS
    OBQ3 --- TAX PROCEDURE CAL 
    OBBG --- ASSIGN COUNTRY TO TAX PROC
    OVK3 --- CUSTOMER TAX CATEGORY 
    OVK4 --- MATERIAL TAX CATEGORY 
    OVK1 --- TAX DETERMINATION RULES 
    OVK6 --- ASSIGN DELIVERY PLANTS
    and thenVK11 to maintain the condition record for the tax rate. 
    I raise a sales order and is getting a error stating that "sales area is not defined".
    1) At SPRO>SD>Sales header-->Assign Sales area to Sales document - Combine your Sales Organisations, Distribution Channels & Divisons
    2) At VOPA-->Assign Partner Determination procedure to your Account Group of Customer Master you are using.
    3) At VOPA--> Assign Partner Functions to your Account Group & Partner Determination procedure
    Steps to create a Vendor Master Data at the client level and how do we extend it to different company codes?
    Follow the following steps:
      1. Create a vendor account group   OBD3
      2. Define no. range for vendor account group    XKN1
      3. Assign number range to Vendor account group   OBAS
      4. Define tolerance Group for vendor     OBA3
      5. Create 2 GL accounts    FS00
              a) Purchases A/c
              b) S. creditors A/c
      6. Create Vendor master data     XK01
      7. change/block vendor master data   XK02/XK05
      8. Define document type and no. range     OBA7
            a) KA
            b) KG
            c) KR
            d) KZ    *-- Vandna
    How to find the strategy group in sap sd?
    Menu path for Strategy Group is:
    Spro --> Production --> Production Planning --> Demand Management --> Planned Independent Requirements --> Planning Strategy --> Define Strategy Group.
    OPPT -- Maintain Starategy Group
    We can see Strategy Group in Material Master Record - MRP 3 - Planning -- Strategy Group.
      10 - For Make to Order
      20 - For Make to Stock
    Where do we maintain "Item Category Usage" at the master level?
    Spro --> Sales and Distribution --> Sales --> Sales Documents --> Sales Document Item --> Define Item Category Usage
    Item Category Usage: item category usages which control the usage of an item. Item category usage controls, for example, the system response if during document processing an item does not refer to a material but to a text item. Item category usage can also be maintained via the item categories 
    In contracts we are creating quantity contract and value contracts in that we only put the validity period after validity period that contract will close,but customer want before one month closing the period system should alert with popup box like this contract is going to close, for this sales manager can follow up the customer for renual the contract.
    Getting a pop-up when the Contract is going to expire is not a Standard SAP thing.  For this you need to do some programming.  Instead of this the Std system has a reminder system where in the open Contracts and Quotaions are popped up when you about to create a sales order.
    This setting is in the Sales order header ,
    Goto -- VOV8 --- Quotation and Outline agreement messages
    If you want to have different number range for different sales area where the settings to be done.
    Number Rage are use to define what number to be assign to sales document type. Number range can be assign Internal or external.
    In internal number range system automatically assign a number to sales document according to number range define in system.
    In External number range user manually assign number to sales document.
    For Assigning Number Range use T-Code VN01
    Choose Intervals -
    Define your number range
    Hope this helps you.
    Do award points if you found them useful.
    Regards,
    Rakesh
    P.S. you can send me a mail at my mail id [email protected] for any specific details

  • BADI for restrict creation of business transaction independently

    Hello Experts,
    I have a requirement where I need to check if the Business activity (say any 'Z' transaction) has a opportunity follow-up document then only that business transaction need to be executed else should give the error that "Z transaction need to be created through opportunity only and can not be created individually".
    I found one BADI CRM_ORDERADM_H_BADI where I can check for the condition but the issue is that as soon as I entered to CRMD_ORDER this BADI gets triggered where I need to trigger this BADI only when the user is trying to create the 'Z' business transaction individually.
    Any Suggestion will be highly appreciated.
    Thanks in Advance & Best Regards,
    Deepak Gupta

    Deepak, there is a parameter called CRM_MODE and this has the following values depending upon the transaction context:
    A - Create
    B - Change
    C - Display and
    D - Delete
    Now, in the same BAdI, since you are restricting the creation of the activity, check the CRM_MODE for the Activity, if it is A, then, call the function module CRM_ORDER_READ with the GUID of the activity and extract only the document flow ET_DOC_FLOW. Check this export table and see if the parent is an opportunity (BUS2000111). If your condition is not met, add an Error message in the transaction.

  • Order Status Report (by CO Business Transaction

    Hi All,
    At present, we are using standard IO Reports that give output of all the Orders (even closed ones). User wants a Report that gives output (or in other words they can select) by "status" of the order (e.g. they don't want to see whatever happended in closed orders).
    I think it will be done by copy and then modify SAP standard report. Would you please suggest which field/table is used and how to go about it.
    I know brought "Business Transaction" in General Data selection and created/applied a variable as ZVRNGR, but, can not proceed further as it does not select BFRE/BTAB or BABS..
    In the maintenance of Number Range Interval for Controlling Documents, I do not see / can't select the elements BFRE (Released), BTAB (Technically Complete) or BABS (Closed). I think these ionle
    Would anyone of you please explain the solution, with step-wise details.
    Thanks in advance.
    SB

    Thanks Sree.
    The problem is that in Report Painter's Library, view CCSS is being used and option sare limited to the fields.
    One of the fields is CO Business Transaction, but, here it does not work when I select (BFRE, BTAB or BABS) for Sattus of the Order. And these 4-digit IDs are also not there in config under KANK.
    Does it make any sense to you (or anyone else). I know one guy, Hein who has the idea about it.
    For WBS, are you having report in Report Painter or is it ABAP?
    Thanks again,
    SB

Maybe you are looking for