SAP ABAP IMG Activity SIMG_EXG_0035 (Maintain Exchanges user exits)
Hierarchy
☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM (Application Component) Customer Relationship Management
     ⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       ⤷ OIA (Package) Exg exchanges
IMG Activity
ID SIMG_EXG_0035 Maintain Exchanges user exits  
Transaction Code S_SO5_65000053   IMG activity: SIMG_EXG_0035 
Created on 19990913    
Customizing Attributes SIMG_EXG_0035   Maintain Exchanges user exits 
Customizing Activity SIMG_EXG_0035   Maintain Exchanges user exits 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SIMG_EXG_0035    

Description

In order to make Exchanges user exits as flexible as possible, many of the calculation rules and details of movements and financial values, for example, are specified in user exit routines and are thus fully customizable.

All the routines for Exchanges are found under this menu, where they can be created, displayed and changed.

Example

Requirements

Standard settings

Recommendation

Activities

To define your own Exchange routines, proceed as follows:

  1. First check whether you can use the IS-Oil routines delivered with the standard system.
  2. Either overwrite an existing routine or select a group number from the number range reserved for customer modifications (600 - 699) and enter the corresponding description. The recommendation is to always copy an existing routine and modify as required.
  3. Program the routine in the editor.
  4. Activate the routine.
  5. Enter a long text that describes the meaning of the routine in more detail.
  6. Enter the routine number in the appropriate customizing transaction.

Further notes

Below you will find a short description of the IS-Oil standard Exchange routines:

  • Fee Pricing
  • Exchange Transactions
  • Exchange Statement

Fee Pricing

  • Maintain fee pricing invoice verification

    Used to specify the date that fee repricing is based upon in the invoice verification process. Examples provided are:

Exchange Transactions

  • Invoice netting cycle

    Used to specify the way that the netting cycle gets set in the billing document. The default setting is a copy from the delivery item details. However, this exit can be used so that for example a certain billing type is always set to specific netting cycle.

    User exit set via customizing - Maintain billing and netting document types

  • Determine payment term

    Used to determine the payment terms to be applied to the billing document header. The default setting is that if there is only one invoicing cycle being used, then the payment term is taken from the cycle level payment term field. Otherwise, if there are more than one invoicing cycle being processed or a cycle level payment term does not exist, the payment term is taken from the reference document item (as per standard SAP).

    User exit set via customizing - Maintain billing and netting document types

  • LIA pricing strategy

    Used to determine the price for the value of the logical inventory movement for a book receipt or book delivery. This is the value that updates the internal receivable/payable accounts and OIA07. The examples provided are:

    • Current logical inventory price (i.e. from OIA07)
    • Current physical inventory price (i.e. from the material master MBEW)
    • Use associated location (as per price reference plant)

      User exit set via customizing - Maintain company code control

  • LIS communication structure from MM

    Used to allow user-specific processing of the S036 structure before the database update when processing material movements. For example, the field S036-MATREF can be filled as required here.

    Note: no customizing option, routine 600 is the only valid option.

  • LIS communication structure from LIA

    Used to allow user-specific processing of the S036 structure before the database update when processing LIA book receipts and book deliveries. For example, the field S036-MATREF can be filled as required here.

    User exit set via customizing - Define LIA document types

  • Exchange assignment
    • Delivery
      • Used when a delivery is created or changed to define logic that will automatically select and assign purchase orders to supply the delivery. For example, if certain plants are only supplied via defined exchanges, then a user-defined table of plants and exchange purchase order numbers may be referenced here.
      User exit set via customizing - Define item categories for deliveries
    • Bulk shipment
      • Used when a bulk shipment is created or changed to define logic that will automatically select and assign purchase orders to supply the shipment.
      User exit set via customizing - Define bulk shipment type
  • Additional exchange data

    Used to display additional information for the sales and purchasing contracts in the exchange assignment list. A 22-character field exists that can be filled via this user exit with fields from the sales or purchasing contracts to facilitate the selection of contracts for processing. The example routine provided gives the valid-to-date for the contract and the creator ID.

    User exit set via customizing - Define exchange types

  • Exchange base prod. price

    Used to determine the calculation method for determining the logical inventory value when a sub/base product relationship exists for the exchange.

    Two example routines are provided:

    • Check for stock at the receiving/delivering plant of the base product and, if found, use the material value there to calculate the logical inventory value. Otherwise, if there is no stock, then get the price from the price reference plant for the base product for the logical inventory value.
    • Get the price from the price reference plant for the base product to use to determine the logical inventory value.

      User exit set via customizing - Define exchange types, but also changeable in the exchange header.

  • Check sub/base product

    Check to validate the sub-product to base product relationship. Two examples are given:

    • Check the relationship within one document. This means that for a specific sales or purchasing contract if two or more line items are created for the same material, the base product must be the same for all of those items.
    • Check all exchange documents. This is the similar to the first example, except the check is across all sales and purchasing contracts within the specific exchange.

      Not set via customizing, but defined upon exchange header.

Exchange statement

The following user exits relate to both the exchange statement function and the movements based netting function.

  • Communication structure format

    The following user exits relate to the formatting and display of the exchange statement and the movements based netting document.

    User exit set via customizing - Assign format exits to output types

    • Statement header
      • Used to write out a header for the exchange statement. The example routine writes out the date and page number.
    • Exchange heading
      • Used to prepare the fields for the exchange heading. The default information is the exchange number and partner reference, but only if a routine is specified, even if it is a blank routine.
    • Receipts
      • Used to prepare and format the output of the receipt details. Example routines provided are for accumulating the receipts by plant, by alternate destination (external details) etc.
    • Issues (deliveries)
      • Used to prepare and format the output of the issues details. Example routines provided are for the summary report and detail report.
    • LIA (Logical inventory adjustments)
      • Used to prepare and format the output of the LIA details. Example routines provided are for the summary report and the detail report.
    • Pure financial adj.
      • Used to prepare and format the output of the pure financial details. Example routines provided are for the summary report and netting summary.
    • Summary
      • Used to prepare and format additional output at the end of the exchange statement. If nothing is specified in the user exit, the default output is Net Due Us, Net Due You etc.
    • Statement footer
      • Used to write out a footer for the exchange statement.
  • Error handling

    Used to control the way in which inconsistencies found during processing the exchanges data are handled, e.g. deliveries that are not fully invoiced. The example routine prepares and outputs notes on the exchange statement.

    User exit set via customizing - Assign format exits to output types

  • Movements index selection

    Used to allow customization of the routine that selects the movement documents from the exchanges movements index (OIAQB).

    User exit set via customizing - Maintain exchange output document types

  • Financial document selection

    Used to specify the selection of the financial documents for the exchange statement. The selection co

Business Attributes
ASAP Roadmap ID 201   Make global settings 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG SIMG_EXG_0035 0 I270009305 Exchanges 
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
VOFM T - Individual transaction object O54R EXG_0035 Maintain IS-OIL User Exits 
History
Last changed by/on SAP  20031202 
SAP Release Created in