SAP ABAP IMG Activity BADI_PUR_SALESORDER (Business-to-Business for Sales Order Processing)
Hierarchy
☛ SAP_APPL (Software Component) Logistics and Accounting
   ⤷ CA (Application Component) Cross-Application Components
     ⤷ OPS_EHP_SWITCHES (Package) Enhancement Package Coding Switches for ERP Operations
IMG Activity
ID BADI_PUR_SALESORDER Business-to-Business for Sales Order Processing  
Transaction Code S_E38_98000117   (empty) 
Created on 20070820    
Customizing Attributes BADI_PUR_SALESORDER   Business-to-Business for Sales Order Processing 
Customizing Activity BADI_PUR_SALESORDER   Business-to-Business for Sales Order Processing 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name BADI_PUR_SALESORDER    

Use

You can use this Business Add-In to control the Business-to-Business (B2B) inbound message processing for the ordering process.

Technical data:

  • Message type: PurchaseOrderCancellationRequest
  • Name space: http://sap.com/xi/APPL/Global2

Not all data required for creating, changing, or deleting a sales order is contained in the B2B message.You can therefore use BAdI methods to control the following actions:

  • Set data
  • Override data set by the system (for example, due to settings in the system or in Customizing)

The following are examples for using each method:

  • DEFINE_SALESDOCUMENT_TYPE

    This method enables you to override the order type from Customizing.
    This is useful, for example, when you create a sales order. The standard system derives the order type from Customizing.

  • DEFINE_PARTYID_TO_CUSTOMER

    This method enables you to check and override the customer number determination.
    In B2B messages it is possible that the customer's internal customer number is included in the message for the sales person.

  • DEFINE_CUSTOMER_TO_SALES_ORG

    This method enables you to check and override the sales area data.
    The sales area data is not included in the B2B message. You define the derivation of the sales area data in Customizing.

  • DEFINE_PAYMENTTERMS

    This method enables you to check and override the terms of payment.
    The terms of payment of an order are derived from the customer data and sales area data.

  • DEFINE_CANCELLATION_REASON

    This method enables you to define the reason for rejection.
    If the message sends the deletion of an order item, a reason for rejection for the affected item is mandatory in the sales order. Without this definition, the system cannot carry out the rejection of an item.

  • DEFINE_PRODUCT_TO_MATNR

    This method enables you to check and override the material number.
    In B2B messages, the internal material number is not included in the message.

  • ERROR_FOLLOW_UP

    This method enables you to start individual follow-up activities. This is useful, for example, if the B2B message cannot be sent due to an error.

  • DEFINE_SALES_CUSTOMER

    This method enables you to determine the customer number.

Activities

For information about implementing BAdIs as part of the Enhancement Concept, see SAP Library for SAP NetWeaver under BAdIs - Embedding in the Enhancement Framework.

Business Attributes
ASAP Roadmap ID 151   Design interfaces 
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 BADI_PUR_SALESORDER 0 HLA0009601 Sales 
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20070820 
SAP Release Created in 603