SAP ABAP IMG Activity OLMROMRY (Enter Program Parameters)
Hierarchy
☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM (Application Component) Customer Relationship Management
     ⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       ⤷ MRM (Package) Appl.development R/3 decentralized invoice verification
IMG Activity
ID OLMROMRY Enter Program Parameters  
Transaction Code S_ALR_87099743   (empty) 
Created on 19990319    
Customizing Attributes OLMROMRY   Enter Program Parameters 
Customizing Activity SIMG_CFMENUOLMROMRY   Enter Program Parameters 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name OLMROMRY    

In this Customizing activity, you define the control parameters for posting EDI incoming invoices.

Enter the following parameters:

In the Posting Information group box, specify the following:

  • Which document type the system is to use when an invoice is sent via EDI
  • Which document type the system is to use when a credit memo is sent via EDI

The other settings depend on whether you want to enter invoices received via EDI in Invoice Verification or in Differential Invoicing (you configure this in EDI Partner Profiles).

  • Logistics Invoice Verification

    Define how the system reacts when there are differences between the values received via EDI and the values proposed by the system. Enter the following in the Logistics Invoice Verification only area:

    Processing type

    Blank:

    The invoice document is posted using the invoice data. If the invoice contains quantity or price variances, the system blocks it for payment.

    1:

    The invoice document is entered as containing unclarified errors and saved with the values proposed by the system and the values contained in the EDI invoice. You have to manually process the parked invoice document later.

    2:

    The invoice document is posted with the values determined by the system. The EDI invoice is reduced by the amount of the variance.

    3:

    Depending on the positive small difference configured in the vendor-specific tolerances, the invoice document is created as follows: The system first compares the positive small difference tolerance limit with the total of the positive variances of the invoice items in an invoice. Positive differences arise when the invoice value transmitted via EDI is greater than the value proposed by the system.

    • If the positive difference is smaller than the positive small difference tolerance limit, the invoice is posted with a quantity or price variance and the system blocks it for payment.
    • If the positive difference is greater than the positive small difference tolerance limit, the invoice is parked as containing an unclarified error and you must process it manually.

      4:
      The invoice document is checked against the tolerances in accordance with online processing. You maintain the tolerance keys on a company-code-specific basis and use them to determine which variances are checked.


      Checking material numbers and units of measure
      Define whether the material numbers and units of measure in the EDI invoice are to be compared to those in the purchase order items. Note that the invoice cannot be posted if there are variances.

Standard settings

Recommendation

Activities

Further notes

Business Attributes
ASAP Roadmap ID 204   Establish Functions and Processes 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 1   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 OLMROMRY 0 HLA0006615 Invoice Verification 
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
V_076S_M V - View SM30 0000000000 Generated Table Maintenance: V_076S_M 
History
Last changed by/on SAP  19990319 
SAP Release Created in