SAP S/4HANA SD flashcards
SAP S/4HANA SD · Build recall with a focused review session.
32 cards. Read the term and the definition here. The deck at the top of this page is optional.
- Business partner roles
- Roles such as customer, supplier, and contact person determine which data and transactions a business partner can use; one partner can hold several roles simultaneously.
- Business partner categories
- Organization, Person, and Group classify partners. Organization represents legal entities, Person represents natural persons, and Group represents informal groups; category controls fields and numbering.
- CVI in S/4HANA
- Customer-Vendor Integration synchronizes business partner data with customer and vendor roles. In SAP S/4HANA, customers and vendors are business partner roles rather than separate master records.
- Business partner grouping
- Grouping assigns number ranges and field status to business partners. It determines whether numbers are internal or external and which fields are required, optional, or hidden.
- Business partner blocking
- Central, company-code, and sales-area blocks prevent a business partner from being used in new transactions. Existing documents remain; blocking is used for credit or compliance holds.
- Business partner relationships
- Relationships link two partners using a relationship type and direction, such as contact person or spouse. They support shared addresses and contact data.
- Business partner duplicate check
- The duplicate check compares new partner data against existing records using match groups and search strategies; it can issue warnings or errors before saving.
- Billing due list
- Transaction VF04 collects delivery- and order-related items that are due for billing. It supports collective billing, split criteria, and creation of multiple billing documents.
- Delivery-related billing
- Billing created from a delivery uses the delivery quantity and goods issue date. The delivery item must be billing-relevant, and billing block must be cleared.
- Order-related billing
- Billing created directly from a sales order without a delivery, often for services; it uses order quantity and a billing plan or date.
- Credit memo request
- A sales document type used to request a credit memo. After approval, billing creates a credit memo that reduces revenue and posts to FI.
- Billing document cancellation
- Transaction VF11 reverses a billing document. It creates a cancellation document and reverses the FI posting; billing documents are not deleted.
- Billing split criteria
- Rules that divide a billing due list into separate billing documents, for example by sold-to party, payer, plant, or billing date.
- Account determination billing
- Billing uses condition technique with account keys to post revenue, discounts, and taxes to FI. The pricing procedure and account determination procedure must match.
- Delivery due list
- Transaction VL10 selects sales orders due for delivery based on dates and shipping point, enabling collective creation of outbound deliveries.
- Goods issue posting
- Posting goods issue reduces inventory and creates material and FI documents. It sets the delivery goods movement status and is the basis for delivery-related billing.
- Delivery item category
- Controls delivery processing for an item, including picking relevance, packing relevance, and whether goods issue is allowed.
- Shipping point determination
- Shipping point is determined from plant, shipping conditions, and loading group; it controls delivery scheduling and goods issue.
- Delivery split
- A delivery can be split by route, plant, storage location, or shipping point to reflect different processing requirements.
- Returns delivery
- A delivery document type used to receive goods back from a customer; it can trigger a returns credit memo and inventory posting.
- Condition technique
- Pricing uses condition types, condition tables, access sequences, and pricing procedures to determine prices, discounts, surcharges, and taxes automatically.
- Pricing procedure determination
- The pricing procedure is found from sales area, document pricing procedure, and customer pricing procedure in customizing.
- Access sequence
- An access sequence defines the order in which the system searches condition tables to find a valid condition record.
- Condition exclusion
- Condition exclusion prevents duplicate or competing condition types from both applying, for example two base prices.
- Statistical condition type
- A statistical condition is calculated and displayed but does not change the net value or subtotal of the pricing procedure.
- Condition scales
- Scales define different condition amounts by quantity or value ranges, such as tiered discounts; scale basis and type control calculation.
- Sales document types
- Document types such as OR, RE, CR, DR, and CS control sales order processing, number ranges, item categories, and copy control.
- Sales area
- Combination of sales organization, distribution channel, and division that determines pricing, plant determination, and output.
- Item category
- Controls whether a sales item is relevant for pricing, delivery, and billing and which schedule line categories are allowed.
- Schedule line category
- Determines delivery and availability processing for a sales order schedule line, including whether a delivery is created.
- Copy control
- Customizing that links source and target documents, such as order to delivery and delivery to billing, controlling data transfer and requirements.
- Incompletion procedure
- Defines required fields in sales documents; missing data causes an incompletion log that can block subsequent processing.