There are five pillars to the SAP Fiori user experiences paradigm: Role-based (Decomposition into task-based experience) Responsive (All sizes, devices, versions, channels) Simple (1-1-3) (I User, 1 Use case, 3 Screens) Coherent Apps that speak the same lenguage) Instant value (Low barrier to adoption).
Various user types can be found, depending on the structure of the specialized area and the IT department, as well as the degree of digitization. However, in almost every company, there are three basic user types: Occasional user Expert or key user Developer or programmer.
What's SAP Fiori? Transaction apps offer task-based access to tasks like change, create, display (documents, master records), or entire processes with guided navigation. Analytical apps provide insight to action. They give you a visual overview of complex topics for monitoring or tracking purposes. Factsheets give you the opportunity to search and explore your data. They provide a 360 degree view on essential information about an object, and contextual navigation between related objects.
Company Code: A company code is the smallest organizational unit of Financial Accounting for which a complete, self-contained set of accounts can be drawn up for purposes of external accounting. .
The following personalization options are available in the SAP Fiori launchpad: Adding applications from the catalogs assigned to them. Removing applications that you do not want to use. Modifying and adding applications for filtered report results.
Sales Organization: At least one sales organization has to be defined in the system and each one has to be uniquely assigned to a company code. However, more than one sales organization can be assigned to a single company code.
Distribution Channel: Distribution channels have to be assigned to at least one sales organization (multiple assignments are possible). To use the sales and distribution functions, you need to define at least one distribution channel in the system.
Divisions: Several Divisions can be assigned to a Sales Organization. To use the sales and distribution functions in the system, at least one division has to be defined in the system.
Divisions definition: Several Divisions can be assigned to a Sales Organization. To use the sales and distribution functions in the system, at least one division has to be defined in the system.
The following information concerning the usage of plants within sales and distribution processes is important: To use the sales and distribution functions in the system, you need at least one plant. Each plant is uniquely assigned to a company code. To use a plant within a sales and distribution process, it has to be assigned to at least one combination of a sales organization and a distribution channel. Multiple assignments are possible. The plant is essential for determining the shipping point.
Warehouse Management: Warehouse management functions are often needed in addition to the functions of inventory management. For example, a company wants to track the amount of materials in every storage bin, and wants to control and record all movements of goods and materials in the warehouse. To support this, SAP Extended Warehouse Management (EWM) is embedded in SAP S/4HANA. For the activation of the corresponding warehouse management functions, combinations of plants and storage locations are linked with a warehouse number.
Extended Warehouse Management: The warehouse number is the highest level organizational unit in warehouse management. In practice, the warehouse number usually corresponds to a physical building or distribution center. Each warehouse number has a substructure that maps the spatial relationship in the warehouse complex in detail. There are different areas where products are physically stored in a warehouse. These areas, called storage types, include various types of racks, goods receipt areas, and goods issue areas. Storage types are represented as a group of warehouse bins with similar characteristics. Storage sections are subdivisions of a storage type. A storage section represents a group of bins that have a common attribute, for example bins that are used to store fast-moving items. Storage sections are used when determining the putaway storage bin. Storage bins are the lowest level of the organizational structure. They are assigned to a storage type and a storage section (if one exists). Storage bins represent the physical locations where goods are stored in the warehouse.
Pre-sales activities include: Entering and tracking customer contacts. Mailing campaigns. Answering customer telephone queries. Inquiries Quotations.
Sales Orders normally contain: Customer and material information. Price information for all financial statement items. Information about delivery dates and delivery quantities. Information about shipping processing. Information about billing.
Sourcing, The material can be sourced as follows: Directly from stock By replenishment from a vendor (via a purchase requisition or a purchase order) By replenishment through own production (via a planned order or a production order).
Sourcing, in this process step in SD you can: Check the availability of the ordered goods Transfer the requirements to materials planning.
Sourcing, MM organizes and monitors the actual sourcing process, this can include: Existing stock In-house production External procurement.
The creation of outbound deliveries is the first step in the shipping process. The outbound delivery controls, supports, and monitors numerous process steps, such as the following: Picking and confirming via warehouse management functions (optional) Packing (optional) Transport planning and monitoring via shipment documents (optional) or via freight orders in SAP S/4HANA Transportation Management (also optional) Posting the goods issue.
When a Billing document is created, the general ledger accounts are normally determined automatically and the relevant data is posted. The system creates the following: A Debit posting on the customer’s receivables account A credit posting on the revenue account.
Billing supports: Creating invoices for goods and services Creating credit and debit memos Canceling previously posted billing documents Automatically transferring billing document data to accounting.
Process Flow: Depending on the document from which you call the process flow, all the relevant preceding and subsequent documents are displayed. The main processing status can also be tracked in this way and it is possible to navigate to the fact sheets of the respective documents. The process flow displays the process as a graphic and is available via corresponding apps (such as Manage Sales Orders) on the SAP Fiori launchpad.
Sales Processing If a relevant preceding document exists, data can be copied from it when the sales document is created. For example, one or more quotations can serve as reference documents for a sales order. In this case, the system copies the relevant data to the sales order and the user does not have to maintain everything manually.
To combine items from multiple orders in a single outbound delivery, they must all have these same values: Shipping point Due date Ship-to address.
Schedule Lines in Outbound Deliveries Unlike sales documents, delivery documents do not contain schedule lines. Each schedule line in the sales document can become an item in the delivery document.
Warehouse Management – Connection to SAP EWM. To execute physical goods movements in the warehouse, "warehouse tasks" are used. Warehouse tasks are needed for the following: Picking Putaway Internal movements Posting changes GR postings GI postings.
Results of posting Good Issues: Inventory management:
The quantity in inventory management and the delivery requirements in materials planning are updated. Balance sheet accounts:
The value change in the balance sheet accounts for inventory accounting is posted (the postings from the relevant accounting document are based on the cost of the material). Financial accounting:
Additional documents are created for financial accounting. Billing due list:
The respective delivery can now be used as basis for billing. Status update:
The status in all the associated documents is updated.
Combining multiple Outbound Deliveries into a Billing Document. These documents should have these same values: Destination country Billing date Payer.
Billing Document Structure Header level:
The data for the document header is valid for the entire document. This includes, for example, data about the payer and the billing date. Item level:
Each item in the billing document contains its own data. This includes, for example, details about the material, billing quantities, and net values for the items. .
When the Billing Document is saved, the following occurs: Debit posting on the customer receivables account Credit posting on the revenue account. The status is updated in all the related sales, delivery, and billing documents. The customer's credit limit data is updated (if the corresponding function is used).
Incoming Payment: When an incoming payment is posted, the data on the relevant G/L accounts is posted automatically. The system does the following: Posts a debit on the cash account Enters a credit memo on the customer’s receivables account.
Source of Data for Sales Documents. Data sources include, for example, the following: BusinessPartner master data (customer) Material master data CMIR: (this master data can be used to maintain customer-specific material numbers) Condition master data: this master data is relevant for automatic pricing. Output Master Data: (outputs are used to send information to the customer via various media, such as mail, electronic data interchange (EDI), or fax. Control tables : (these tables are maintained in Customizing. Depending on the table settings, the proposal can be controlled by a variety of data in the sales documents) A previous sales document can also serve as a data source for another sales document. Example: a quotation can serve as a data source for a sales order.
Business Partner Category Person Organization Group.
Mandatory Partner functions. Sold-to party: The customer who places the order. Ship-to party: The customer who receives the goods or services. Bill-to party: The customer who receives the invoice. Payer: The customer who pays the invoice.
Cross-Division Sales. You can adjust these parameters to control the following: Whether the division on item level is copied from the corresponding material master record or whether the division in the document header is also relevant for the items. How the system should respond (no reaction, warning message, or error message) if the materials in the sales order have a different division compared to the header.
Customer Material Info Record (CMIR). The following information in particular can be maintained in the customer-material info record: The reference from the customer’s material number to your material number. A customer-specific material description. Material-specific shipping information for the customer (such as delivery tolerances, control of partial deliveries, default value for the delivering plant).
Condition Master Records in Pricing. The condition type controls the properties of the condition master record, including the following: Condition class (for example, price or discount). Scales (are scales allowed and is a value or quantity scale possible?). Level (is the data record relevant for the header and/or item level of the document?). Validity period (a default value can be proposed).
Output Master Data: Output information can be send to the customer via various media, such as mail or (EDI). As with pricing, output determination
- takes place using the Condition Technique.
- In the output master data, you define the Transmission Medium (for example, printer or fax),
- the Time of the output creation,
- and the Partner Function (who will receive the output) for an output type. Output can be:
- Sent immediately when saving
- Or by using a standard program (RSNAST00) that is run regularly.
The form (layout) of an output can be defined by using different tools. The form is then assigned to an output type.
SAP S/4HANA output management. This technique is based on Business Rule Framework Plus (BRFplus), a set of decision tables used by the system to identify the correct output type, output medium, printer settings and so on. SAP S/4HANA output management is the strategic output management framework for SAP S/4HANA and future developments will be delivered only in this framework. Adobe XFA is the default technology for form templates, but legacy forms, such as SAPscript, SmartForms and Adobe Forms, are still supported. The major benefits of the new approach are as follows: Flexible and powerful output parameter determination. Unified solution across the applications: SD, MM, FI and so on. Full integration with SAP Fiori apps. State-of-the-art email support: flexible configuration, multiple recipients and email templates.
In contrast with classical output management based on output master data, SAP S/4HANA output management supports only: Print e-mail XML IDoc .
Item Proposals: If a customer frequently orders the same combination of materials, or if you recommend a particular selection of products for an opening order, you can store the frequently used data as an item proposal to reduce the time needed during sales order processing. - If you wish, the item proposal may also include proposed order quantities.
- You can display a list of assigned customers for each sales item proposal. During sales order processing, you can then retrieve all or some of the materials and quantity data from the item proposal directly into your sales document. Items proposed from an item proposal can still be changed in the sales order.
Plant is relevant for the following functions: Tax determination Availability check Determination of the responsible shipping point.
Sources for automatic Plant determination are in this order: 1. CMIR 2. Ship-to-Party 3. Material Master Record.
Shipping Point is relevant for the following functions: Delivery scheduling Route determination Delivery creation.
Automatic Shipping Point Determination: Shipping Conditions in (Sold-to-Party or Ship-to-Party) Loading Group in (Material: General/Plant Data tab) Delivery Plant in (CMIR, Ship-to-Party or Material).
Route is relevant for the following functions: Transit time: the amount of time the goods are in transit. Transportation lead time: the amount of time needed to organize the means of transport.
Determining the Route Automatically: Departure Zone of Shipping Point Shipping Conditions in (Sold-to-Party or Ship-to-Party) Transportation Group in (Material) Transportation Zone of the Ship-to-Party.
Time Components for Delivery and Transportation Scheduling: Pick/Pack time: Time for picking and packing the material Loading time: Time for loading (for example, onto the truck) Transportation lead time: Time for preparing the transport (for example, determining the forwarding agent) Transit time: Time for transporting the goods to the customer.
Backward Scheduling includes: Transit Time / Loading Time / Transportation Lead Time / Pick/Pack Time The calculated Material availability date and the Transportation Planning date are of special importance. The system uses the longer of these two times when scheduling deliveries --> Transportation Lead Time and Pick/Pack Time.
Forward Scheduling includes: Pick/Pack Time / Transportation Lead Time / Loading Time / Transit Time If the complete quantity of the ordered material can be confirmed for the calculated new material availability date, two schedule lines are generated for the corresponding sales document item, as follows:
● The date of the first schedule line corresponds to the customer’s requested delivery date and has no confirmed quantity.
● The date of the second schedule line shows the confirmed delivery date and the confirmed quantity.
An availability check is carried out during sales order processing if: The material requires an availability check. The availability check is set in Customizing for this transaction.
The material availability check in sales orders is performed at "plant level" for the corresponding item. During automatic determination, the system looks for a valid default value for the plant in the relevant master data using the following sequence: 1. CMIR 2. Ship-to party customer master record 3. Material master record.
You can influence the "SCOPE OF THE AVAILABILITY CHECK" with entries in certain Customizing control tables. Among other things, you can configure: Types of stock (for example, safety stock, stock in transfer, or stock in quality inspection), Inward movements (for example, purchase or production orders) Outward movements (for example, sales orders, reservations from materials management).
PARTIAL DELIVERY AGREEMENT: Maintain the corresponding parameters within the customer-material information record and/or within the business partner master data. The main options for partial deliveries on item level are: Multiple partial deliveries are allowed. Only one delivery should be created (even if the ordered quantity can’t be fulfilled). Only a complete delivery (per item) is allowed. No limit to subsequent deliveries.
Which master record is the source to determine this Complete Delivery indicator? The indicator is proposed from the business partner master record.
Which master data is used to propose the Partial delivery/Item indicator in the order item? The default value for the indicator can be maintained in the customer-material info record and in the business partner master record. If a customer-material info record exists, the value for the indicator is taken from this source.
BACKORDER PROCESSING. An Order is a backorder if: The quantity of an order item is not completely confirmed. The required delivery date for an order item cannot be kept.
BACKORDER PROCESSING - Confirmation Strategies WIN. Confirm as requested. Shall be fully confirmed in time. GAIN. Improve if possible. Shall at least keep the confirmation and should gain. REDISTRIBUTE. Redistribute. Should gain, but may also lose. FILL. Delete confirmation, if required shall not gain anything, should keep confirmation, but may also lose. LOSE. Delete confirmation. Shall lose everything.
BACKORDER PROCESSING - Before the backorder processing (BOP) can be executed, several elements have to be prepared. BOP Segments BOP Variant BOP Run.
COLLECTIVE PROCESSING - Worklist When you want to create follow-up documents of sales orders you can often do this via collective processing. The procedure is very similar, irrespective of which type of document you want to create. First, select all the documents for which you want to create the corresponding follow-up documents. Second, create the subsequent documents.
SPLIT CRITERIA Different ship-to parties in sales orders / No combination into a single outbound delivery Different shipping points in sales orders / No combination into a single outbound delivery Different payment terms in sales orders / No combination into a single billing document.
Collective Processing – Deliveries. The relevant sales orders can be selected by various criteria, such as: - Shipping Point
- Delivery creation date This function can be used in the following ways:
Background processing: Use a batch job to be executed during off-peak hours.
Online processing: Use the corresponding app (for example, Create Outbound Deliveries).
Examples for Creation of Outbound Deliveries. The following scenarios are good examples: The customer requires complete delivery: This adjustment means that all quantities of all items in a particular sales order should be delivered in a single outbound delivery. The customer does not require complete delivery: You can define a partial delivery agreement with the customer. The customer allows orders to be combined: This means that the customer allows items in multiple sales orders to be combined into a single outbound delivery during collective processing. .
COMBINING ITEMS from different sales orders is only possible if the items have several common characteristics, for example: Shipping point Delivery date. Ship-to-Party Route Incoterms.
Examples for creation of Outbound Deliveries Complete Delivery: Order --> Delivery Partial Delivery: Order --> Delivery / Delivery Order / Order: Delivery.
COLLECTIVE PROCESSING - Billing Common characteristics are:
- Billing date
- Payer
- Terms of payment. Invoice split: You have a sales order for which one outbound delivery has been created. If some of the above mentioned relevant characteristics of the preceding items are not the same, multiple billing documents are created. Collective invoice: You have two sales orders for which three outbound deliveries are created (for example, different ship-to party or partial delivery). A single billing document is created with reference to the outbound deliveries. Separate billing document for each outbound delivery: You have a sales order for which two outbound deliveries are created. Two billing documents are created with reference to these.
PRE SALES DOCUMENTS: With regard to documents in SAP S/4HANA, the following two major sales document categories are relevant during the presales phase of the sales process: Inquiries: You receive inquiries from your customers, for example, about material prices or delivery dates. Quotations: Based on these inquiries, you can create corresponding quotations to provide the customers with the information they need. However, when creating quotations, referencing inquiries is optional, and quotations can also be created from scratch.
Does automatic pricing take place during entry of quotations or inquiries? Yes. Automatic pricing takes place (dependent on customizing) during inquiry and quotation creation.
Do you have the option of carrying out the availability check in an inquiry or a quotation as you do in the sales order? Yes. An availability check is carried out during inquiry and quotation entry in the same way as during sales order entry (dependent on customizing).
Service Products Standard Material Type: DIEN (Service) No Inventory Management. Item Category Group: LEIS (Service Without Delivery) Material Master Views: Basic Data / Classification / SD data / Purchasing / Accounting.
Identify the correct sequence for make-to-order process flow, from the sales order to the production order. 1. An individual customer requirement is generated from the sales order. 2. An individual customer requirement is transferred to materials planning. 3. Material requirements planning (MRP) generates a planned order for the material automatically. 4. A production order is created for the final product by converting the planned order. 5. The system transfers the confirmed quantity and material availability date from the production order to the sales order.
Credit and Debit Memo Requests Credit and debit memo requests can be created with reference to a billing document or a sales order. When the documents are created, the system asks you to enter an order reason for evaluation purposes. When you create a credit/debit memo request, the document automatically contains a billing block. This block prevents the document from being billed immediately. Once the complaint has been checked by the responsible employees, the credit/debit memo request can be released by removing the billing block. After the billing block has been removed, the corresponding billing documents can be created and the required accounting documents are generated automatically.
Credit Memo Request Workflow With the Manage Credit Memo Request Workflow app, you can configure the workflow to optimize the approval process for credit memo requests. The app allows you to define conditions under which to automatically release credit memo requests as well as to define approvers for requests that need to be verified. If a workflow is activated and the configured start conditions are fulfilled, the approval process is initiated. Business process specialists can define sales teams with their team members and approvers. Configuration experts can define and activate credit memo request workflows with their thresholds and agents. Sales managers can then receive notifications (My Inbox or Notifications) for credit memo requests waiting for approval. The manager can decide to approve, to reject, or to ask internal sales representatives to rework credit memo requests.
Cancellation of Billing Documents - A separate billing document (cancellation billing document) is created.
- A new accounting document are generated.
- This reverses all the postings made as a result of the incorrect billing document by re posting each posting item with the opposite symbol.
Goods Return The returns document can be created with reference to a billing document or a sales order. In this way, the system captures all the necessary data about quantities and price agreements from the original document. When you create the returns document, the system asks you to maintain an order reason (for example, Damaged in Transit) for evaluation purposes. In addition, the document automatically contains a billing block to prevent a credit memo from being created immediately. When the goods arrive at your warehouse, the corresponding goods receipt has to be posted. To do so, a returns delivery has to be created first with reference to the returns document. The relevant quantity is usually posted to a separate returns stock category rather than to the unrestricted-use stock.
FREE OF CHARGE REPLACEMENT Rather than a credit, the customer may request a free of charge replacement for the returned goods. In this case, instead of a credit memo, a subsequent delivery free of charge sales document is created with reference to the returns document. This subsequent delivery free of charge document is then delivered (but not billed).
SAP Smart Business Combines real time insights with analytics and transactional follow-up activities to allow better and faster decisions. New consumer grade, responsive and consistent user interfaces supporting multiple channels. It follows SAP Fiori guidelines and concepts, such as the SAP Fiori navigation. It helps you to easily identify exceptions with (KPI) visualizations that use semantic colors based on targets and thresholds that have been defined. It also offers SAP Fiori apps (SAP Smart Business modeler apps) for easy configuration of your KPIs and their visual appearance. You can jump directly from a data point in the chart to the relevant transaction to solve the issue. .
SAP Sales Order Fulfillment app Role-based access to all relevant info such as KPI, news feeds, and specific tasks New working model supporting end-to-end insight to action scenarios. Users can easily adapt the user interface to their needs based on drag and drop and a powerful tile catalog. New coherent and responsive user experience Color-coded visualization of violated thresholds SAP Smart Business is an open framework.
SAP Sales Order Fulfillment app. The app offers a list of all sales orders that cannot be processed for one or more reasons. It has the following features: Highlights impediments Provides supporting information Provides specific options to resolve issues.
SAP Smart Business for Sales Order Fulfillment features: Process incomplete data Unconfirmed quantities Billing blocks Delivery blocks in SO and other delivery issues Shipping blocks in Deliveries and other shipping issues Invoice issues and accounting issues for invoices Issues in supply, in purchase, and manufacturing orders.
Issue Solving in Sales Orders – Resolve Billing Block: Display header information and the list of blocked items Display details for each blocked item Remove the billing block on header level and/or item level Check and edit the payment terms on header and/or item level Navigate to the Change Sales Order app to make further changes.
Managing Sales Plans Sales plans can be used to set sales targets for an upcoming period (for example, the next year). The desired target values can be planned by using various dimensions, such as customer, material and/or organizational units. - With the Manage Sales Plans app, these dimensions can easily be selected.
- Then a corresponding plan layout can be generated and downloaded to Microsoft Excel.
- After the target values have been maintained in the Excel file, it can be uploaded back into the sales plan.
Sales Performance – Plan/Actual - After sales plans have been created for a planned period, the sales performance can be tracked by comparing the actual values to the target values.
- It can be monitored in real time to what extent the sales targets are being achieved and thus insights into the current sales performance can be gained. The Sales Performance – Plan/Actual app offers a hybrid view in which you can effectively visualize the difference between plan and actual data in a chart while display the details in a table. Planned and actual values represent either incoming sales orders or sales volume, depending on what you have planned in the selected sales plan version. Planned and actual values are compared by month, quarter, or year within the planned period, depending on how you have defined this in the selected sales plan version.
Analytical Apps OLTP: Create sales orders, invoices, and accounting documents, and display customer master data OLAP: Dunning, check the available quantity, operational reporting (list open sales orders). .
Today's data management systems are optimized either for daily transactional or for analytical workloads. This separation leads to the following drawbacks: The OLAP system does not have the most up-to-date data. The OLAP system only has a predefined subset of the data. A resource-intensive extract, transform and load (ETL) process is needed to synchronize the data in both systems. Data redundancy is introduced. Different data schemes introduce complexity for applications that combine sources.
Available Analytical content in SAP S/4 HANA Sales Incoming Orders Sales Volume
- Flexible Analysis
- Check open Sales
- Profit Margin.
SAP S/4HANA Real-Time Analytics Architecture No latency and no data duplication Part of the general extensibility concept Ready-to-use content Integration scenarios with SAP BW Full ABAP Lifecycle integration Supporting ERP authorizations and hierarchies Supporting more business cases (Analytics, search, fact sheets). Read access for search/fact sheets is also supported.
LIVE TRANSACTIONAL DATA With SAP S/4HANA this concept is supported using Core Data Services (CDS) for real-time operational reporting. The content is represented as a virtual data model (VDM), which is based on the transactional and master data tables of SAP S/4HANA. Views are developed, maintained, and extended in the ABAP layer of the SAP S/4HANA system. The system generates SQL-Runtime-Views in SAP HANA to execute the data read and transformation inside the SAP HANA database layer.
SAP S/4HANA Real-Time Analytics Architecture The advantages of this approach include full ABAP integration, allowing for instances to re-use existing reporting authorizations, and so on. Also, SAP can make use of the analytical engine (embedded BW functionality) to support an elaborate hierarchy display. These advantages allow for the creation of many more use cases for the VDM; SAP S/4HANA analytics support not only generic operational OLAP reporting but also scenarios of embedded analytics for hybrid transactional and analytical applications (such as embedded SAP BI or SAP Smart Business Cockpits) based on the same models. Read access for search/fact sheets is also supported.
End User: Multidimensional Report includes all explorative analysis tasks which focus on: Unexpected business questions. Ad-hoc filtering Pivoting Sorting Rearranging of data in tabular Graphical UIs is supported A Web Dynpro grid is used in this context.
This options offers a hybrid view for sales orders in which you can effectively visualize the difference between plan and actual data. Sales Performance — Plan/Actual.
COMPLETE and PARTIAL DELIVERY INDICATOR You can set the COMPLETE delivery indicator in the sold-to party master record, and this is then transferred to the document header of the sales document. It specifies that a document and all of its items must be delivered in full. The PARTIAL delivery indicator for the document items can be proposed from the sold-to party master record or the customer material info record. The information in the customer material info record takes precedence. It refers to the full or split delivery of several schedule lines for an item.
The following partial delivery agreements are possible at item level: Partial delivery allowed Create a delivery with quantity greater than zero Create only one delivery (also with quantity = 0) Only complete delivery allowed No limit to subsequent deliveries.
Using the ATP Check in the Sales Process - In the sales process within the SAP system, the availability check can be used in all sales documents that have the “schedule line” level.
- It can also be used in outbound deliveries. .
Monitor Material Coverage Net. The following navigation options are supported: Navigate to the Manage Change Requests app to place and manage your requests. Navigate to the Monitor Material Coverage app to get an overview of your materials. Navigate to other apps to access further information or change material data.
SCHEDULE LINE CATEGORY. The system uses two steps to automatically determine the schedule line category to control the order schedule lines: First, it tries to determine the schedule line category using the key combination of item category and MRP type. If a schedule line category is not found, the system then finds the schedule line category using only the item category.
ORDER ITEM CATEGORY. This is determined on the basis of the following criteria: 1. Order type of the document. 2. Item category group from the material master record. 3. Use of the item that is implemented within the program for specific business transactions and functions. 4. Item category of a higher-level item (in the case of a subitem).
DELIVERY ITEM CATEGORY. This is determined on the basis of the following criteria: When you copy an order item to a delivery, the system copies the key of the order item category to the delivery item. To determine the item category, the system takes into account the delivery type as well as the item category group (from the material master of the item). Additional use is set from the system (by coding) for some special functions.
AVAILABILITY CHECK CONTROL The CHECKING GROUP in the Material Master Record, is one feature of determining the “availability check control. The second feature for determining the “availability check control” is the CHECKING RULE. The assignment of document type and checking rule is hard-coded (ABAP) in the “Sales and Distribution” application.
The following elements can be included in the availability check: Stocks: Unrestricted, Safety, In transfer, Quality inspection, and Blocked. Receipts/issues: purchase orders, purchase requisitions, planned orders, production orders, reservations, dependent reservations, dependent requirements, sales requirements, and delivery requirements.
ATP for Special Stock For operations that generate special stocks (such as make-to-order production, consignment processing, or returnable packaging processing), availability is checked against the special stock using the specified scope of the check, in conjunction with the respective special stock indicator from the requirement class.
Availability for Sales Documents and Deliveries is generally checked at: Plant at Item level If a storage location is defined in the order item and the storage location check is active, the check is carried out in this storage location only. If the material is handled in batches, an additional check is carried out at batch level. However, you can configure the Customizing settings to deactivate the check at storage location level.
Calculating the Replenishment Lead Time For materials produced in house, the following options are available. If the Total RLT field (MRP 3 View) is maintained, the time maintained in this field is used for the availability check. If the Total RLT field is not maintained, the system reads the in-house production time (MRP 2 view) and, if available, the goods receipt processing time (MRP 2 view) and interprets the total of these two times as the replenishment lead time for the availability check. For materials procured externally, it is not useful to maintain the Total RLT field. For external procurement, the total of the purchase processing time (Customizing: Materials Management → Purchasing → Purchase Requisition → Processing Time), planned delivery time (MRP 2 view), and goods receipt processing time (MRP 2 view) is always interpreted as the replenishment lead time for the availability check.
Advanced Availability Check - Product Availability Check (PAC) Scope of Check Scheduling Check levels Replenishment lead time Temporary quantity assignments Delivery groups.
Advanced Availability Check - Product Allocations (PAL) Features: Planning quantity restrictions Flexible aggregation level at which the restrictions are planned By defining periods, time-related rationing is possible Can determine the requested quantity from another period and if previous or subsequent periods are considered. Combination of restrictions:
Logical AND
Logical OR.
Advanced Availability Check - Release for Delivery (RefDy) Features: FIORI based interactive changes to Sales Order confirmations before releasing the orders to delivery Impact simulation of current ATP situation Direct navigation to Sales Order Display of Batch and Allocation restrictions Visual representation of the stock situation of a material/plant.
Advanced Availability Check - Alternative Based Confirmations (ABC) Features: Determination of the delivering plant with best availability during during Sales Order creation Simple configuration of Alternative Control that allows to activate ABC based on a combination of characteristics Configuration of substitution strategy that allows to specify how to rank alternatives based on SAP Delivered attributes.
Advanced Availability Check - Product Allocations (PAL) Features: Simple and flexible set up Time dependent assignment to product/plant Hierarchical / Sequential allocations Excel download and upload for mass maintenance Importing / exporting allocations quantities from external systems Display and analyze product allocation availability situation Supports PAC, PAL and ABC.
Advanced Availability Check - Back Order Processing (BOP) Features: Requirement segmentation and classification: Win, Gain, Redistribute, Fill and Lose Filter and Sorter for each segment FIORI based set up and result monitor Supply Assignment (ARun) Exception handling with fall back variants. Supports Product Allocations Global Filters to restrict product and location selection.
App. Product Allocation Overview as a Cockpit. From here you can open the following three apps to further analyze and drill down into allocation and order data Monitor Product Allocation Periods Monitor Product Allocation Characteristics Combinations Monitor Product Allocation Order Items.
Release for Delivery (App), main features: Display sales orders containing materials for which you are responsible during a specific time period, including sales order items for materials with limited availability Display the potential financial impact for your organization if materials are not available and material redistribution is not optimized Manually redistribute material quantities between sales order items, as required, to fulfill a sales order partially or completely Apply confirmation strategies such as Confirm from Top to enable efficient, semi-automatic processing of mass data. Protect quantities of sales order items from further processing Postpone further processing of sales order items Release materials for delivery, thus triggering subsequent logistics processes (for example, picking).
SAP FIORI Apps for Backorder Processing, general restrictions: The item does not belong to a checking group or if the checking group is not configured for advanced product availability checks. The requirements class to which an item belongs is empty or is not configured for product availability checks, including product availability checks against product allocation. The Advanced ATP functions have not been activated in Customizing. The Fixed Date and Quantity flag is set in the sales order document.
Organizational units mandatory in SD: Sales organization Distribution channel Division Sales area.
The following activities can be performed in a division: You can define division-specific master data for customers and conditions. Use a common division to create shared customer master data and conditions that are valid for several divisions. Determine that all the items in a sales document belong to the same division for each sales document type. The items in a delivery or billing document can belong to different divisions. Define different ways of printing the output based on the sales documents for each division. Use the division as a selection criterion for listing sales documents and creating a delivery worklist.
Business Area Account Assignment A business area is an organizational unit in (FI). It is the smallest organizational unit within a company code and can be used in financial reporting. It usually represents a discrete line of business.
The following organizational units are optional in SD: Sales Office Sales group Salespersons.
Shared Master Data At the sales organization and distribution channel level, you can define which distribution channel is used to access condition records and which distribution channel is used to access customer and material master data. At the sales organization and division level, you can define the division used to access condition records and customer master data. The organizational data specified in the document is transferred to the SAP Business Information Warehouse (BW) and SAP Business Intelligence reporting tools from the sales, delivery, and billing documents. .
Document Flow You can use copying control to map specific requirements of your business processes and activate other options such as update document flow. The document flow is updated at the document header level by default. If the Update Document Flow checkbox is selected in copying control at item level, the document flow is updated for individual items too. You can navigate from the document flow to the relevant documents display screen. You can also display additional data about the status of a document listed in the document flow.
The levels for COPYING CONTROL for sales documents are as follows: Header Item Schedule line Copying Requirements: Before data is copied from the source document to the target document, certain requirements must be met. ABAP routines contain these requirements, which are assigned in the copying control tables using their identification (ID) numbers.
Copy Control – Header Level. The details screen contains the following options: Copying Requirements Data transfer routines Whether item numbers should be copied from the source to the target document Complete Reference check box.
Copy Control – Item Level. The details screen contains the following options: Pos./Neg. Quantity Copy quantity Copy Requirements Update Document Flow Copy Schedule Lines.
Copy Control – Schedule Line Category. The details screen contains the following options: Proposed schedule line category Copying requirements.
Completion Rule. The completion rules for an item category are as follows: An item is complete as soon as it is referenced (Completion rule A). An item is only completed once the full quantity has been copied into a subsequent document (Completion rule B). You can select the completion rule for each item category in Customizing. If an item is rejected, Not referenced or completed status is shown in the source document.
Copy Control Order - Delivery to Billing Document From delivery you receive the goods issue dates, which are important for the payment terms of the invoice. Billing copy control is maintained at header and item levels.
Text Sources CUSTOMER: Central Texts (FI + SD + Contact Person) texts MATERIAL: (Purchase Order + Sales) Texts CUSTOMER MATERIAL: (Customer Material) texts DOCUMENT: (Header + Item) texts.
Texts in Business Processes. In business processes, you can use texts in the following ways: Store texts in the master data and copy them from the master data into sales and distribution documents. Copy texts from a reference document to another sales and distribution document, for example, from a quotation to an order or from an order to a delivery document. Copy texts in a specific language. Determine the conditions for copying the texts. Copy a standard text into a sales document, for example, Christmas greetings.
Text control determination: 1. Create a text type for a document text object. 2. Define text determination procedures and access sequence. 3. Assign the text type to the defined text determination procedures. 4. Assign the text determination procedure to the relevant document type or item category. 5. Define specific controls for each text type, such as the inclusion of a text type in the incompleteness log.
For the text determination procedures of a document, you can specify the following features: Whether the text should be mandatory (the text must be included in the incompleteness log). Whether the text should be determined automatically. Whether the text should be displayed in a text window (popup) when it is transferred to the document.
Which of the following text sources can you access in the material master? Marketing notes Delivery text Sales text.
Which of the following statements are true? You can store texts in the master data and copy them into sales and distribution (SD) documents. You can specify the conditions under which texts are to be copied.
Which of the following features can you specify for document text determination procedures used for text control? Whether a text needs to be copied or referenced. Whether a text needs to be determined automatically.
Communication Strategy A communication strategy represents a sequence of communication types. You can use a communication strategy for external transmission. The communication strategy is used to search through the sequence of given communication types until it finds the communication data for the required address, which is taken from Central Address Management. You can define the communication strategy using the additional data for the output condition record.
The available Output timings are as follows: A standard program (RSNAST00), that is set to run at regular intervals, selects the output to be sent. You can decide whether an output must be selected the next time the program runs (transmission timing 1) or at a time specified by the user (transmission timing 2). A special selection program, designed for different sales documents (for example, deliveries and billing documents), processes output online or in batches (transmission timing 3). You can schedule a batch to ensure regular processing (as for timing 1). The output is issued automatically as soon as a document is posted (transmission timing 4).
Output is determined using condition technique. 1. Condition Table 2. Access Sequence 3. Condition Types 4. Output Determination Procedure 5. Output Determination Procedure Assignment.
A form modification is simple if it meets the following prerequisites: The field exists in the communication structure. The field is not contained in the form. The field can be integrated into the form in an existing format.
New Output Determination. The main benefits of the new approach are the following: Extensibility: broad usage of CDS views. BRFplus: flexible and powerful output parameter determination. Unified solution across the applications: SD, MM, FI, and so on. SAP Fiori: full integration with SAP Fiori apps. State-of-the-art email support: flexible configuration, multiple recipients, and email templates. In contrast to the output management based on NAST, the new output management supports only the print, email, XML, and IDoc (for on premise) channels. Other channels are not available by default.
When using condition-based output, which of the following functions can be used to check which output types were determined and based on which selection criteria? Create Change.
Which of the following correctly describes how a BRFplus output decision table is processed? Every row in the table is processed in sequence. Table rows can be arranged so that the most specific sets of conditions are evaluated first.
Options available for enhancing an SAP S/4HANA system. Customizing: Implementation Guide (IMG). Modification: Source code is open, and in the ABAP Workbench, you will find the tools you need. Enhancement: If there is no opportunity to customize your requirement, you can use enhancements or customer developments. Customer Development: Customer development involves the creation of new repository objects.
The available enhancement techniques include: User Exit Customer Exit Business Transaction Events (BTEs) Business Add-Ins Enhancement Points Enhancement Sections.
Field selection for material master records depends on the following factors: The transaction in use The procurement type E or F of specific material The material type The actual plant The industry sector that you have assigned to the material The SAP system.
In SD, you can use transaction VOFM to create and process routines for the following functions: Copying requirements: Data transfers: Requirements and formulae:.
User Exit A user exit is a point in an SAP program where a customer subroutine can be called. The customer subroutine is edited in special INCLUDES. These INCLUDES are special because of how they are used (they are not special for any technical reasons). They contain empty FORM routines, which are the user exits. These routines are called by the respective processing programs. They are delivered only once during System implementation. They are never overwritten. Customers can edit their own subroutines here.
Customer Exit Customer exits allow customers to enhance their application functions. Customer exits are pre-planned by SAP. Generally, they consist of several components. SAP application programmers create SAP enhancements from program exits, menu exits and screen exits. A management function is provided for this purpose (transaction code SMOD).
Business Transaction Events (BTEs) BTEs allow you to implement additional logic in standard code, similar to program exits. SAP application programmers determine where to place BTEs in standard code, and what data the system needs to transfer at each point. They also create sample function modules, complete with short texts, an interface (function module parameters), and documentation, and describe the functions that are possible with the enhancement in the accompanying SAP documentation.
Business Add-Ins Architecture Business Add-Ins (BAdIs), unlike customer exits, take into account the changes to the software delivery process. In the figure, Classic Business Add-Ins: Architecture, the upper section displays the typical delivery landscape. It no longer consists only of provider and user. Instead, it can now contain a whole chain of intermediate providers. The lower section outlines how BAdIs function. An SAP application program provides the enhancement option. This requires at least one interface and a BAdI adapter class that implements it.
Components of BAdIs Interface Generated class Filtering Control.
Enhancement Options: are options to define the following without making modifications: Additional (optional) interface parameters in SAP function modules and SAP methods Additional attributes and methods in SAP classes Preparation or post-processing functions for global SAP methods Replacements for global SAP methods.
Which of the following functions in Sales and Distribution use the condition technique for system modification? Pricing Output control Account determination.
Which factors can influence the status of fields in field selection in material master records? Material type Plant Industry sector.
Which of the following statements are true about Business Transaction Events (BTEs)? Additional components can be attached to the SAP system. Predefined interfaces allow customer access. Additional logic is always defined by SAP.
Structure of Condition Records Condition records are always defined for a key combination that is assigned to the respective condition type. You can also assign several possible key combinations to a condition type, You can specify a validity period to limit a pricing agreement to a specific period. You can define the values in a condition record, such as price, surcharge, and discount, according to a scale. There is no limit to the number of scale levels. You can specify an upper limit and a lower limit for each condition record. If you want to manually change the pricing elements that are determined by the system, you can do so only within these limits.
Conditions in the Document Header You can enter conditions at the document header level. These are known as header conditions and are valid for all items. The system automatically distributes these header conditions among the items based on the net value. The basis for distributing the header conditions can be changed in the pricing procedure by selecting the appropriate routine.
The following criteria influence how pricing procedures are determined: The Sales Area The document pricing procedure code in the document type The customer pricing procedure code in the customer master record.
What is controlled by the condition type? Calculation Type Amount Scales.
Source Fields for Access Sequences. Within each access of an access sequence, you can specify the document field or source field with which an access is performed. Examples Material or pricing material Document currency or local currency Sold-to party or ship-to party.
Pricing Elements Condition table: The condition table defines the key fields of the condition records. Access sequence: The access sequence contains the hierarchy for the condition record access. Condition type: The condition type represents the properties of the pricing conditions. Pricing procedure: The pricing procedure defines how the condition types are linked. Procedure determination: The procedure determination selects the correct pricing procedure.
The following elements may be necessary to implement pricing elements for complex scenarios: New fields for pricing: Create new fields to meet customer requirements. Requirement routines: Define dependencies and improve performance. Formulas: Expand the limits of standard configuration to meet unique user-specific requirements.
Release Procedure for Conditions: The following statuses are currently defined: Released Blocked Released for pricing simulation (net price list) Released for planning and pricing simulation (planning in Controlling and Profitability Analysis) The release status is set indirectly by defining a processing status in Customizing for pricing and assigning a release status to the processing status.
Calculation Type The calculation type for a condition type is defined in Customizing. This calculation type determines how prices or discounts and surcharges are calculated for a condition. When creating new condition records, you can select a calculation type that differs from the one set in Customizing for condition type.
Price List Output. You can: Display price lists directly in the system: If you have entered a layout, the system uses this layout to determine how the price list is displayed. Upload price lists to an FTP server. E-mail price lists as Microsoft Excel spreadsheets or character separated values (including in the ZIP file format) to sold-to parties.
Condition Records Maintenance by Using Pricing Reports. Condition maintenance has two maintenance interfaces. The new interface allows mass maintenance of conditions based on characteristics, such as the customer. You can maintain condition records across all condition types and condition tables. For example, you can display and maintain the material prices, discounts, and surcharges for a customer in a single step. You can also run the previous maintenance transaction for conditions by choosing the Select using condition type node. Through this interface, you can maintain only the condition records of the condition type that you have chosen.
App Manage Prices - Sales. Features Search for Condition Records Create Condition Records Copy selected Condition Records Edit Condition Records Export and Import Condition Records Importing a template-based spreadsheet.
What options do you have for the condition record maintenance besides the condition type based maintenance (transaction codes VK11, VK12, VK13) ? You can maintain Condition Records with Manage Price sales app. You can only maintain Condition Records which are configured as condition determined manually in the pricing procedure.
Group Conditions with Varying Keys. The formulas available in the Group Condition Routine field are as follows: Formula 1 (complete document):
This formula adds the quantities or values of all the line items in the sales document that have the same condition type as the group condition that is currently being processed. Formula 2 (for all condition types):
This formula adds the quantities or values of all the line items in the sales document, irrespective of which condition types have been applied. Formula 3 (material group):
This formula adds the quantities or values of all the line items in the sales document that have the same material pricing group (KONDM field) as the current sales document line item.
Excluding Conditions Conditions can be linked to requirements in the pricing procedure. A requirement can evaluate the condition exclusion indicator and, if this indicator is set, ignore the condition. The condition exclusion indicator can be set in either the condition type or the condition record. You can create your own exclusion indicators and test for the existence of the indicator in the requirement routines.
Condition Supplements Condition supplements do not have their own access sequence. Condition supplements are found and maintained with the underlying condition record of condition type PR00. You define the set of allowed condition supplements in Customizing for the main condition type. You can do this by assigning a different pricing procedure (PR0000) to the condition type that lists the required condition supplements.
Using Special Condition Types Header condition type HM00 allows you to enter the order value manually. The system then distributes the new order value proportionally between the items, taking into account the previous net item value. The system determines the taxes again for each item. Condition type PN00 allows you to specify the net price for an item manually. The system deactivates the original conditions. You can create a minimum value for each order by using condition type AMIW. If the value in the order header is less than this minimum order value during pricing, the system uses the minimum value as the net order value automatically. The minimum order value is a statistical condition.
Condition type AMIW is a group condition and is divided among all the items according to value. You can create a minimum price for a material by using condition type PMIN. If the minimum price is not met during pricing, the system determines the difference by using condition type PMIN.
Customer Hierarchy. The steps to create a customer hierarchy are as follows: 1. Create master records for each node. 2. Assign the nodes to each other. 3. Assign the customer master records to the relevant nodes. You can move the hierarchy nodes. If you move a node, the system automatically reassigns all related nodes and customer master records. You can assign price or rebate agreements to a high-level node within a customer hierarchy. The agreements are then valid for customers at all the subordinate levels of this node.
Discounts and SurchargesFigure Pallet Discount KP00: The pallet discount offers the customer a discount for whole units of measure only, such as a complete pallet. This is controlled by basic formula 22 in the pricing procedure. This formula only takes the number of complete pallets into account. Incomplete Pallet Surcharge KP01: In incomplete pallet surcharge KP01, the customer pays a surcharge for an incomplete pallet. This is controlled in basic formula 24 in the pricing procedure. This formula tests the quantity for a fractional portion. Mixed Pallet Discount KP02: Mixed pallet discount KP02 accumulates the quantities of individual items and calculates the discount for complete pallets only. This calculation is controlled by condition type KP02 (the group condition is selected and the unit of measure is PAL) and the corresponding condition record. Condition Type DIFF: Determines the difference amount. This condition type is a group condition that is distributed among all the items according to value.
Cost VPRS The standard SAP system uses condition type VPRS to retrieve the standard cost of the material. In the pricing procedure, this condition type is marked as statistical. By using condition category G, condition type VPRS accesses the valuation segment of the material master to determine either the standard cost or the moving average cost, as specified in the material master. Condition category S always accesses the standard cost, whereas condition category T always accesses the moving average cost.
Cash Discount SKTO In the standard SAP system, condition type SKTO is used to retrieve the cash discount rate. In the pricing procedure, this condition type is marked as statistical. The system accesses table T052 by using condition category E. The system then calculates the amount from the first percentage rate of the item payment terms.
Customer Expected Price - EDI1 and EDI2. You can either accept or decline the customer-expected price, or you can reject the sales document item: If you accept the customer-expected price, you can manually adjust, for example, the value of the net price within the app. If you decline the customer-expected price for a sales document item, the system releases it for further document processing with the net price. If you reject the item, the item is not processed any further. You can use this action, for example, if you cannot agree on a net price and the customer does not want the item anymore.
Statistical and Relevant for Account Determination You use this indicator to define that the statistical price condition is posted to account-based Profitability Analysis (CO-PA) as journal entry to an extension ledger of Financial Accounting. You do this to increase and improve information relevant for management reporting. In sales, you do not have any effect of this field, it just shows the condition type marked as statistical. The actual effect and information is only available in CO-PA. This statistical condition value is posted as a journal entry to an extension ledger of Financial Accounting.
Criteria for Tax Determination Departure Country (Country of the Delivering Plant) Destination Country (Country of the Ship-to-Party) Customer Classification (For business within the EU on the basis of the tax number STCEG) Material Tax Classification (Access with departure country) .
Which of the following factors are considered when determining tax rates? The business transaction (domestic, export, or import) The tax liability of the ship-to party The tax liability of the material.
Which of the following condition types are group conditions and are divided among all the items in an order according to value? AMIW (Minimum Order Values) HM00 (Manual Order Value).
Which condition types are statistical? VPRS (Cost (price) SKTO (Cash Discount).
Which document displays the sales deal and promotion information? Sales Order Billing Document.
Condition Contract Management Configuration. The configuration of Condition Contract Management comprises three main steps: 1. Configure Pricing including Condition Contract Conditions: 2. Configure Condition Contract Maintenance: 3. Configure Condition Contract Settlement:.
Condition Contract — Settlement Types. The following settlement types are available: Partial settlement Final settlement Delta settlement Delta accruals.
Condition Contract — Accrual Conditions. Use Cases in the Order-to-Cash Process. The basic sales scenarios are as follows: Rebates based on billing documents Rebates based on cash sale data Rebates based on agreed budgets.
Flexible Reporting. Features Performance critical reports are built based on newest CDS view technologies and IDA ALV Supports customer specific fields Flexible selection option supported SAP Hana optimized.
In which order should the specified steps be executed when configuring pricing including condition contract conditions? 1. Check condition tables 2. Specify contract condition relevant for condition types 3. Assign condition type to condition type group 4. Define pricing procedures.
OData Service for Condition Records. Integration - Price Management. Pricing Condition Record in Sales - Delete: This OData service enables customers, partners, and external applications to delete condition records in SAP S/4 HANA Sales. Pricing Condition Record (A2A) in Purchasing - Create, Update, Delete: This OData service enables customers, partners, and external applications to create/update/delete condition records in SAP S/4 HANA Purchasing. Enable customers from external systems to delete condition records in SAP S/4 HANA Sales. Enable customers from external systems to create/update/delete condition records in SAP S/4 HANA Purchasing. Enable full integration of external systems / applications with pricing process in SAP S/4 HANA .
OData Service for Condition Records. SAP offers several APIs for Order and Contract Management. You can use APIs to connect business processes across your system landscape and integrate with external consumers of your services. Both OData and SOAP APIs are provided. For pricing, you have the option Condition Record for Pricing in Sales – Replicate and Condition Record for Pricing in Sales – Create, Read, Update, Delete.
Sources for Document Data Master Data Existing Document Data Customizing Hard-coded controls.
Proposing Order Data from Master Data Master Data - Conditions Master Data - Output Master Data - Texts Master Data - CMIR Master Data - Customer Master Master Data - Material Master.
BP Category Business Partner Category: Determines field control (Name, Gender, marital status) Business Partner Grouping: Determines number range (Internal, external) Business Partner Rol: (Determines screen sequence and field control).
You can use the following functions to display and edit BP Roles in the dialog: Overview of all roles assigned to a business partner Deletion of a role assignment Time-based validity of a role assignment Where-used list for a role (for example, in an application).
The standard BP Categories are: Natural person (private individual) Organization (for example: company, department in a company, club, association) Group (for example: married couple, shared living arrangement).
When you enter a sales document, you can also enter the ship-to party instead of the sold-to party. The system then determines the sold-to party from the ship-to party: If there is exactly one sold-to party for the ship-to party, the system can do this automatically. If there are several possible sold-to parties for the ship-to party, the system displays a selection screen with the possible alternatives. If a sold-to party cannot be determined, the system issues an error message in the status bar. A message also appears if you entered a ship-to party in the sold-to party field inadvertently. The system then continues to process the data as if you had entered the ship-to party in the ship-to party field.
Business Data. You can define business data (such as payment conditions, Incoterms) at document header level or for each item. You can decide in Customizing for the item category whether business data at item level should be able to differ from business data at header level. You define this option separately for each item category. This allows you to create documents containing both items in which the business data must be identical to the sales document header and items that allow different business data.
During Plant search, the system checks several master data records: First, it checks whether it can propose a delivering plant from an entry in the customer-material info record. If the customer-material info record doesn't contain a plant, or if there aren't any customer-material info records, the system checks the customer master record for the ship-to party. If this search is unsuccessful, the delivering plant is determined from the material master record.
Blocks in SD You can set a billing block in the document header and in the individual items. You can customize the delivery block to configure the detailed effects of that block in shipping processing. For example, you can prevent the creation of a delivery in general, or allow processing of the delivery and picking but block the goods issue. You can set a billing block in the document header and in the individual items. You can enter reasons for rejection for one or more items. In copying control, you can stop this item from being copied into subsequent documents. The "Fast change" function enables you to simultaneously block all the items that you have selected in the document.
Reject in SD You can enter a reason for rejection for one or several items. You can create a suitable copying requirement in copying control to prevent these items from being copied into subsequent documents. The "Fast change" function allows you to reject several or all items of a document at the same time. A special button is also available for rejecting all the items in a document. You have the option to limit the choice of order reasons and reason for rejections for the sales processing. If you want to limit the selection options you can assign an order reason to a sales document type and / or sales organization in the SAP customizing.
Customizing for sales documents can be done at header, item, or schedule line level, depending on the structure of the document. The instruments for control are Header Level - Sales Document Type Item Level - Item Category Schedule Line Level - Schedule Line Category.
Basic Functions. You need to configure several general sales functions (basic functions) for the sales documents. These include: Partner determination Pricing Message determination Text determination Material determination Credit management Incompleteness Delivery scheduling.
Functions in the Sales Document Type Number assignment Checks: Division / Open Quotations, Contracts / Info Records Enhancements for Contracts Default values: Date / Billing Type / Delivery Type / Blocks Mandatory Reference.
Item Category Functions: Completion Rule Separate Business Data Schedule Lines permitted Delivery and Billing Relevance Pricing Bills of Material (BOM).
The Item Category controls: Whether business data in the item can be different to that of the document header. Whether pricing applies to the item. Whether and how an item is billed. Whether the item refers to a material or whether it is just a text item. Which incompleteness procedure is used to check the item data.
Item Categories are assigned to sales document types. This assignment is influenced by: The item category group from the material master record. The item category group allows you to group together different materials that behave in a similar way during sales and distribution processes, for example. You can also define new item category groups if needed. The usage for the item, which in some cases is set internally in the program. The system uses TEXT if the user enters an item in the inquiry or quotation by entering data in the "Description" field without specifying a material number. FREE is used for controlling free goods items. The item category of a higher-level item (in the case of a sub-item).
Exploding Bill Of Material (BOM) in Sales Documents In Customizing, you define and assign item categories for the main and sub-items of the BOM in the sales document. A specific item category group assigned to the material master record of the main item defines which item categories are assigned to the main item. To determine how far the BOM should be exploded in the sales document, you need to define the extent of the structure of the item category for the main item. When you determine the sub-items, the system also needs to know the item category of the higher-level item. In Customizing for item categories, you control which item(s) are relevant to pricing and how you want to implement requirements transfer.
Schedule Line Category functions: Goods Movement Delivery relevance Purchasing Availability check Requirements transfer.
Schedule Line Category customizing: Schedule lines contain delivery dates and quantities as well as information about the requirements transfer and inventory management. In Customizing for item categories, you decide if you are going to allow schedule lines for the item. You can assign schedule line categories to each item category. By defining a schedule line category, you determine which schedule lines are actually relevant for delivery. You need to activate the relevant to delivery indicator if you want the goods to be physically delivered. In the schedule line category, you set the movement type to control which changes to quantities and values are posted to inventory accounting. Many of the movement types relevant to sales are between 601 and 699. You can deactivate requirements transfer and availability checks at schedule line level.
Schedule line categories are assigned to item categories. The purpose of this assignment is to and is influenced by: Configure the system to propose a schedule line category automatically when you create an order. Determine the schedule line categories that the user can choose instead of the system proposal MRP: First, it tries to determine the schedule line category using the key combination of item category and MRP type. MRP: If no schedule line category is found, the system searches for the key combination of item category/no MRP type.
Creating Sales Documents with reference: You can create sales documents with reference to documents that already exist. You can use the Selection list button to select one or more items in the referenced document and change the order quantities (Partial / All). You can create a sales document with reference to a preceding document from both the initial screen and during document processing. You can create with reference to inquiries, quotations, sales orders, contracts, scheduling agreements and billing documents.
In the status overview that can be displayed for each document in the document flow, you can quickly find detailed information about: Order Delivery status Outbound delivery Picking status Billing status Billing document Posting status.
Copying Control for Sales Documents. To control the copying procedure, at each level you create: Routines for data transfer: These routines control transfer of fields in the preceding document. Copying Requirements: Here you define requirements that are checked when you create a document with reference. If these requirements are not met in a particular case, the system issues a warning or error message and if necessary, terminates processing. Switches: There are switches for setting specific controls for each transaction.
Examples of Copying Requirements Header level: Copying requirement 001 checks, for instance, whether the sold-to party and the sales area in the source and target document are the same. Item level: Copying requirement 301 checks, for instance, whether the item that is to be used as a copy has a reason for rejection or completed status. Schedule line level: Copying requirement 501 ensures that only schedule lines with an open quantity greater than zero are copied.
What can you maintain in the copying control? Copying requirements Customer master data.
Rush Orders characteristics: Rush order is a sales document type used in the sales from plant process or for when the customer needs to pick up their goods immediately from the warehouse. In the rush order sales document type, the immediate delivery switch and delivery type LF are configured. When you save a rush order, the system automatically creates a delivery of type LF. Once the goods have been withdrawn from the warehouse, picking and posting goods issue can begin. When you create the billing documents (for example, in collective processing), the system prints the invoice papers and sends them to the customer.
Cash Sales characteristics: In the sales document type for cash sales, the immediate delivery switch and delivery type BV are configured. When you save the cash sale, the system automatically creates a delivery of type BV and prints a document that can be given to the customer as an invoice. Once the goods have been withdrawn from the warehouse, picking and posting of the goods issue can begin. A cash invoice can be printed immediately from the order and billing is related to the order. An order-related billing index is generated automatically. This updates the billing due list. Billing type BV is created while the billing due list is being processed. The system does not print invoices during billing. The account receivables do not occur for the customer as they do for rush or standard orders, because the invoice amount is posted directly to a cash account.
Consignment Processing Goods are delivered to the customer but remain the property of the company until they are actually used. An invoice is not created until the customer withdraws goods from the consignment stock. Up until that point, the customer has the right to return consignment goods. You process consignment fill-up with order type KB. The goods issue sets up a special stock at the customer. The goods remain in the valuated stocks of the delivering plant. Consignment issue is processed with order type KE. When goods are issued, both the customer special stock and the stock in the delivering plant are reduced. This transaction is relevant for billing. If the customer returns the goods, you can represent this with order type KA (consignment pick-up). This transaction credits the special customer stock during the goods issue. Like the consignment fill-up, this transaction is not relevant for billing. If you want to reverse a consignment issue, you can process this with document type KR (consignment return). The goods receipt sets up the special stock at the customer's again. A credit memo is generated based on the consignment returns.
Free-of-Charge Delivery and Free-of-Charge Subsequent Delivery You create a delivery free-of-charge document when you want to send your customer a sample, for example. You enter a subsequent delivery free-of-charge document. Customizing for sales document type SDF determines that this transaction requires a preceding document. The relevant copying controls must be set up for all preceding documents that might be used. By activating a delivery block in the sales document type, you ensure that delivery free-of-charge or subsequent delivery free-of-charge transactions are not released for delivery until they have been checked by the relevant employee. In Customizing for item categories, you determine that items in sales document types FD and SD are free of charge (for example, with KLN). You can also decide what happens to these items with regard to pricing and billing there.
Incompletion Log An incompleteness log is a list of all data essential to your company in a sales document that has not yet been entered in the system. You can define these data fields in Customizing for the incompletion procedure. The system goes directly from the incompleteness log to various views, where you can then edit the incomplete data.
Controlling the Incompletion Log The incompletion log differentiates between the following levels: Sales document header / Sales document item / Sales document schedule line. In each procedure, you determine which fields are checked for completion You determine areas of validity by assigning procedures.
- Procedure at header level, Sales document type
- Procedure at item level, Item category
- Procedure at schedule line level, Schedule line cat. You can also flag partner functions, texts, and condition types in pricing as mandatory. If these entries are then missing, a note will appear in the incompletion log.
A status group is assigned to each field in the incompleteness procedure. When you define the status groups, you decide which steps should be prevented if data is missing. Examples: Incomplete for delivery – No delivery is possible Incomplete for billing – No billing is possible Incomplete for pricing – No order confirmation or billing are possible A status group can contain any number of these consequences. This allows you to control the effects of incomplete data separately for each field.
Partner types AP, KU, LI, and PE are defined in partner processing for the Sales and Distribution application module. These are defined as follows: AP Contact person KU Customer LI Vendor PE Personnel.
Partner Determination Procedure Partners appear in the system at various levels, such as in the customer master, sales document header, sales document items, and so on. You can define your own partner determination procedures for each of these levels. A partner determination procedure is where you determine which partner functions may or must appear. You determine areas of validity by assigning procedures.
Customer Master and Account Group. When you define the account group, you determine: For each data field, whether it is displayed or not and whether maintenance is mandatory, optional, or not possible. The number range. A number of other control elements, such as for partners and texts of the customer master.
Outline agreements The two main outline agreements are scheduling agreements and contracts. There are two types of contracts - value and quantity. The simplest and most common type of scheduling agreement is represented in the system by document type DS. Document types for scheduling agreements such as BL or DEL are special cases that are used in the automotive component supplier industry. Rental and maintenance contracts are frequently used in the service industry. Maintenance agreements are signed for products that the customer uses over a long period of time and which need to be serviced during that time.
Scheduling Agreements A scheduling agreement is an outline agreement between you and a sold-to party that is valid for a certain period of time. The scheduling agreement contains fixed delivery dates and quantities. These dates are contained in the schedule lines for the scheduling agreements. Once the scheduling agreement is due for delivery, you can create the delivery as normal or by using a delivery due list. When you enter schedule lines for an item in the scheduling agreement, the system adds up the quantities that have already been entered and compares them to both the target quantity and the quantity already shipped. This gives you an overview of all the open quantities.
Quantity Contracts A contract is an outline agreement between you and your customer that is valid for a certain time period. The contract does not contain any schedule lines, delivery quantities, or delivery dates. The same functions are available in contracts as in orders. You can also agree on special price agreements or delivery times. The customer fulfills the contract with individual releases. Schedule lines are created in the release order when it is placed. The release order is then processed like a standard order. Any special agreements regarding prices or delivery deadlines are copied from the contract. Release orders are created with reference to a contract. This generates a document flow record that allows you to update released quantities and values in the contract.
Value Contracts. A value contract can contain other agreements between you and your customer that are checked in the release orders: Special price agreements Customer restrictions Material restrictions If the check is activated in Customizing, the system issues a message informing you whether there are any valid contracts when you enter a release order. You can change the target values in the contract later on.
Controlling Value Contracts. There are two types of value contracts in the SAP standard system: For WK1, you can specify a product hierarchy or a product proposal module. This contract type will always be proposed if you wish to create a value contract for several materials, or a certain group of materials. All the materials that are in the appropriate product proposal module, or that belong to the specified product hierarchy can then be released. If you do not enter a product proposal module or a product hierarchy in a value contract, then all materials can be released. Value contract WK2 (material-related): This value contract type is mainly for contracts that have one material that is usually configurable. Document type WK1 uses item category WKN. Document type WK2 uses item category WKC. According to what you enter in the item, the system determines the item category with the usage indicator VCTR or the item category group VCIT. In copying control, you can decide at item level if the value contract material should be copied to the release, (WKC) or not (WKN). If a release exceeds the target value in a contract item, you can configure how the system reacts: no response, two different warning messages and an error message.
Determining Dates. If you assign a contract profile to the sales document type, the system automatically determines default values specific to the contract. These could be: Rules for determining start and end of the contract Duration category Subsequent activities Cancellation procedure.
Which of the following statements on Scheduling agreement is correct? The scheduling agreement contains fixed delivery dates and quantities. In the scheduling agreement you can only see the target quantity and not the quantity already shipped.
Which statement on Quantity contracts is correct? The Quantity contract requires release order. The Quantity contract does not contain any schedule lines and delivery quantities.
Which statements on the Value contract (sales document type WK1) are correct? The Value contract specifies that your customer agrees to purchase a fixed value (target amount) of goods and services during a defined period. The Value contract requires release order.
Material Determination. Material determination provides you with a tool for automatically exchanging materials in the sales document. You do not need a material master record for the material number that you are replacing. The condition technique provides you with greater flexibility in material determination. When you process a document, the system automatically searches for valid master records that you created previously in material determination. You can assign a substitution reason to every master record in material determination that defines how the material should be determined. You define the substitution rules in Customizing. During order entry, the material ordered by the customer is replaced by the substitute defined in the master record. The system now continues processing with the substitute (for example, in the availability check, pricing, delivery, billing).
Maintain the master records for material determination. When you process master records, you can: Restrict the validity period of a record Maintain separate entries for each key combination Determine reasons for substitution Save one or more substitutes per master record If there is more than one material defined in the master record for material determination/product selection, the sequence in which they appear defines the priority that they have.
Exclusive and Inclusive Bonus Free goods can be part of the order quantity not included in the invoice. This is called an inclusive bonus quantity. The ordered goods and the free goods both involve the same material. The quantity units of the free goods and ordered goods must be the same. In exclusive bonus quantities, the extra goods are delivered free of charge and are not included in the invoice. This can either be an additional quantity of the goods ordered or it can be another article. Free goods can also take the form of extra goods that are free of charge. These are called exclusive bonus quantities. The exclusive free goods appear in the sales document as a separate, free-of-charge item.
Free Goods in the Sales Order The material that has been ordered is entered as a main item and the free goods material is automatically displayed as a sub-item. The item category determines how the item is controlled later in the business process (for example, for delivery or pricing). Item categories TAN and TANN are used in the standard SAP system. The system determines the free goods automatically by accessing the relevant condition records. The system then accesses the free goods master record with the pricing date.
Free Goods Calculation Rule. When you specify a calculation rule, you decide how the system determines the free goods quantity from the additional and document quantities. The free goods quantity is the quantity from which the discount is calculated (not the minimum quantity). The additional quantity is the quantity delivered free-of-charge. The document quantity is the quantity entered by the person creating the sales order.
Sales-to-Employees Orders Employees select their goods, take them from the shelves, and then proceed to checkout. Since employees can only buy the goods that are in the shop, an availability check and transfer of requirements are not necessary. You should only create orders with a net value. This prevents documents without items or with free items from being created in the system. No individual customer master data for employees is maintained in the system. Employee orders are processed using a collective master record (one-time customer account). As soon as employees have paid, they are given an invoice which serves as a receipt.
The following activities can be completed within shipping processing: Monitoring the deadlines of reference documents due fo shipping Creating and processing outbound deliveries Monitoring the capacity situation in the warehouse Providing support for picking Packing Printing and distributing shipping documents Processing the Goods Issue Controlling.
In shipping processing, you can use a delivery document in the following scenarios: Replenishment delivery Delivery for subcontract orders Delivery from proejct Inbound delivery (shipping notification) Delivery without reference (no sales order necessary to create a delivery) Returns delivery Outbound delivery.
Which delivery document refers to a sales document? Outbound Delivery.
Shipping Point A shipping point can also be set as a goods receipt point, which means the shipping points can also be used for inbound deliveries.
Delivery Item Categories Relevant for Picking Check for over-delivery Picking storage location determination Texts Availability check Check minimum delivery quantity Automatic batch determination Packing Control.
Factors Determining Item Category in the Sales Document Sales document type of the order: Item category group Item category usage Item category of higher-level item.
Additional usages are set internally for the following functions: PACK for generating packing items CHSP for a batch split PSEL for product selection V for inbound deliveries for purchase orders and for deliveries in stock transport processes.
Outbound Delivery - Copy Control. You can specify the following data: Under what conditions is the data copied from the order to the outbound delivery Under what conditions can several orders be combined in an outbound delivery Which data is to be transferred Whether the reference needs to be recorded in the document flow.
You enter delivery relevant settings in the sales order types by maintaining the following fields/settings: Which delivery type the system proposes for the outbound delivery Whether the system proposes a delivery date in the requested delivery date field in the order and how far it is in the future Delivery relevance at the order item category level is valid only for text or value items.
Customizing of the Outbound Delivery Without Order Reference If you create deliveries w/o order reference, you must manually select the delivery type on the initial screen of VL01N - Create Outbound Delivery without Order Reference. In the system, you have to define a default order type in the Customizing for the delivery type. A delivery without reference does not contain a link to any real sales order. The Customizing for this default order type contains the default billing type for billing this delivery. When you enter an item in the delivery without order reference, the system uses item category determination to determine the item category for this item. This order item category decides whether this operation is relevant for billing and which billing procedure is to be used. To create a connection to inventory management for the delivery item, the system must allow schedule lines for the order item category. You can then use the schedule line category determination to determine a schedule line in the order. The movement type defined in the schedule line category controls the goods issue posting of the delivery item.
The system determines shipping conditions for a sales order based on the following priorities: 1. The sales document type 2. The business partner (customer).
The shipping point depends on the following criteria: The delivering plant determined for each order item (from the customer-material information record, the ship-to party customer master record, or the material master record) The shipping requirements (for example, express shipping) in the Shipping Conditions field The required loading equipment within the material master record in the Loading Group field.
Route Determination depends on the following factors The country and departure zone of the shipping point (assigned in Customizing) The shipping condition from the sales document type or the customer master of the sold-to party or ship-to party (depending on the customization of the sales document type) The transportation group assigned to the material The country and transportation zone of the ship-to party (assigned in the customer master record).
The following are some of the features of precise scheduling: The system calculates and displays the results of scheduling to the minute. The system uses the working times of the shipping point. Pick/pack and loading times are specified in hours and minutes.
The route schedule generally contains the following: A route A weekday as the departure date, along with a departure time A list of ship-to parties An itinerary (optional).
Determination of the Picking Location If you do not specify any storage location in the order item, the system determines the storage location when it creates the outbound delivery and copies it into the delivery item. The system determines the picking location based on a rule defined in the delivery type.The following rules are shipped in the standard system:
- MALA: The system determines the picking location based on the shipping point, the delivering plant, and the material’s storage condition that you have defined in the material master.
- RETA and MARA: The system uses these rules mainly in trade scenarios. You can also use the customer exit in SAP enhancement V02V0002 to implement storage location determination. The picking location search is activated for each delivery item category.
Output in Shipping Delivery Note LD00 Packing List PL00 Material Tag GI00 Shipping Order SA00 Quality Certificate LQCA, LQCB Shipping Label 0001 Freight List LL00 Outbound Shipping notification LAVA.
Outbound Delivery Monitor, tasks: Goods issue Loading Transportation Planning Confirmation Picking.
Further Functions in Deliveries Material Substitution Credit and risk management Controllable error message Delivery split by Warehouse Number Group of Outbound Deliveries Dangerous Goods check Export Controls Texts Quantity Checks.
Billing - The header contains the following general data that is valid for the entire billing document: Customer number of the Payer Billing date Net value of the entire billing document.
Billing Types available in the SAP system Invoice and Pro-Forma Invoice Cash sale Credit / Debit Memo Returns Intercompany Billing (Invoice / Credit Memo) Cancellation (Invoice / Credit Memo) Invoice List Credit Memo List.
Billing Type Controls Partners Texts and Outputs Posting Block Special features and FI Interface Account Determination Invoice List type Cancellation Billing Type Number Assignment.
Billing Type Proposal In Customizing for the item category, you can determine whether billing is to be carried out with reference to a delivery or an order. The system proposes a relevant billing type from the underlying sales document type. For example, in delivery-related billing, you invoice a standard order (order type OR) using billing type F2. You can change the proposed value when creating billing documents by entering the required billing type in default data.
Delivery-Related Invoices You can reference either an order or a delivery when creating an invoice. If you want to ensure that goods have already been shipped before an invoice is created, create an invoice with reference to a delivery. For example, reference the delivery of a carpet. You can use an invoice to simultaneously refer to an order and a delivery. For example, you can create a single invoice for goods (the carpet) and service (laying the carpet), as long as the corresponding requirements for combining the two are met.
Cancellation To cancel a billing document, you must create a cancellation document. The system copies data from the reference document into the cancellation and offsets the entry in Financial Accounting. You can use billing document type S2 in the standard system to cancel credit memos. You do not need to make an entry in copying control for cancellations. The parameters to be changed (for example, assignment number and reference number) are stored for each billing type directly in the Cancellation area of the screen. You can also cancel individual items in a billing document. When you cancel a document, you branch to an overview screen containing the original billing document as well as the cancellation billing document.
You can create Credit and Debit Memo requests in the following ways: Without reference to a previous business transaction. With reference to an order. With reference to a billing document. You can control in Customizing whether the system is to set a billing block automatically for a credit or debit memo request.
Workflow Credit Memo Request Credit memo requests are usually blocked for billing (credit) upon creation, until the employee responsible releases this block. If the value of the credit memo request is below a certain minimum limit, the credit memo request can be released automatically by the system. The workflow within the framework of credit memo processing now guarantees that the employee responsible is automatically determined and informed when a credit memo request is created, depending on the value involved. The employee responsible can reject, release, or process the credit memo request. With the app Manage Credit Memo Request Workflow, you can configure the workflow to optimize the approval process for credit memo requests. The app allows you to define conditions under which to automatically release credit memo requests as well as to define approvers for requests that need to be verified. If a workflow is activated and the configured start conditions are fulfilled, the approval process is initiated.
Invoice correction request On one side, credit is granted fully for the incorrect billing item while it is simultaneously debited (automatically created as a debit memo item). The difference created represents the final full amount to be credited. You must create the invoice correction request with reference to the corresponding billing document (no reference to order or inquiry). When creating an invoice correction request, the items are automatically duplicated. This means that for every item in the billing document, a second item is created. The resulting item categories must have opposite + and − values. First all credit memo items are listed, followed by all debit memo items. The reference to the corresponding billing document is created when you specify the preceding document and the preceding item. You cannot change the credit memo item. You can, however, update the corresponding debit memo item according to new characteristics (for example, new pricing or change in quantity). You can delete the credit and debit memos in pairs. You can delete unchanged pairs of items all at once in this way.
Quantity Difference Quantity difference is when you want to process a customer complaint because of a certain amount of damaged or substandard goods. The system corrects the quantity to be billed via the debit memo item. If other item pairs arise from the relevant billing document and these item pairs are unchanged, you can delete them in one step, using the Delete unchanged item function.
Pro Forma Invoices You can create pro forma invoices with reference to orders or deliveries. You do not need to post the goods issue before creating a delivery-related pro forma invoice. You can create as many pro forma invoices as required. This is because the billing status in the reference document is not updated. Data from pro forma invoices is not transferred to Financial Accounting.
Which of the following steps must you perform to cancel a billing document? The items are automatically duplicated and the resulting item categories have opposite + and − values. The credit and debit memos can be deleted in pairs and unchanged pairs of items can be deleted all at once.
Copying Control - In Billing, system administrator determines controls for the following: The header, Target is billing type and the source is sales document type. The item, Target is billing type and the source is sales document type and the item category.
Billing - Controls Found at Header/Item Level The following controls are found at header level:
● Reference document; the documents that may be used as reference for billing.
● Determination of foreign trade data, allocation numbers, reference numbers, and item numbers. The following controls are found at item level:
● Billing quantity: Which quantity should be invoiced – the order or delivery quantity?
● Pricing and exchange rate: Should pricing, for example, be carried out again or should prices from the order be copied over, and at what exchange rate?
● Price source: From where should the conditions in the billing document be carried.
How can you create a billing document? You cannot create a billing document without an existing reference document. You can only use a reference document for a billing document for which the corresponding copy control entry exists.
Which of the following copying control options are available at the item level? Billing quantity Pricing.
Which master data information can be updated during the billing process? Pricing Billing date.
Processing Billing Due Lists If you are working with the billing due list, enter the selection criteria, such as sold-to party, billing date, and destination country. When selecting, you can also decide whether the billing due list should only contain documents that are order-related, delivery-related, or both.
Billing Options.You now have the following billing options: Individual billing documents: An individual billing document is created for all documents marked in the billing due list. No combination is carried out. You branch to transaction VF01 for every document selected. Collective billing documents: All documents marked in the billing due list are billed. The system tries to combine them as much as possible. Processing of the selected documents is carried out in the background. After the documents are processed, you return to the billing due list. Here, icons indicate whether or not a document has been billed successfully. Collective billing documents online: The system branches to the Create Billing Document function (transaction VF01 ). The documents are combined as far as possible according to the usual criteria.
You can make billing settings so that the system does the following automatically when you create billing documents: Enter billing date and type before billing If you enable this setting and choose to create billing documents, the system requests a billing date and the required billing type before creating billing documents. Create separate billing document for each item of billing due list If you enable this setting and choose to create billing documents, the system creates separate billing documents for each item of the billing due list that you have selected. Automatically post billing documents. The system automatically posts all billing documents that you create to accounting and triggers output (for example, an invoice by e-mail). Note that if you do not choose to automatically post billing documents, you must manually post your billing documents using the Manage Billing Documents app. Display billing documents after creation The system generates and displays temporary billing documents for the SD documents that you have selected for billing. You then have the option to save or discard them. Saving converts them to final billing documents, while discarding them returns you to the billing due list.
You want to create billing documents regularly on specific dates. How do you achieve this? Use the billing due list on specific dates. Use a factory calendar and assign it to the customer master record of the payer .
Invoice List Invoice lists are mainly used by purchasing associations, when the head office settles billing documents for all the stores. The head office does not receive individual invoices of all the stores instead the head office receives a single invoice list on specific dates. The invoice list lets you create, at specified time intervals or on specific dates, a list of billing documents (invoices, credit and debit memos) for a particular payer .
Invoice List - Customizing If you have agreed upon a factoring discount, maintain condition type RL00 (factoring discount) as well as condition type MW15. Each billing type to be included in an invoice list must be assigned an invoice list type. Define a factory calendar that specifies when invoice lists are to be created. Enter this factory calendar in the payer customer master record. Maintain condition records for condition type, RL00, for the payer. Create output condition records for the condition types LR00 and RD01.
Which of the following is a split criteria and cause an automatic invoice split? Material Group Terms of payment.
Which statements on the Omnichannel convergent billing and the External Billing Document Requests (EBRS) are correct? Choose the correct answers. With this billing method you can converge the internal and external billing data into a combined customer invoices. You can use a Excel file to upload the external billing data.
Periodic Billing. Periodic billing can be used, for example, for transactions involving rental contracts. The contract data stored in the system can then be used as the basis for creating the billing plan. The start and end dates define the duration of the billing plan. If possible, they are taken from the contract data. If the duration is unlimited, you may decide not to set an end date. In this case, new dates can be extended to the horizon (the horizon specifies the number of settlement periods that are set in the billing plan). You can create new dates either directly in the billing plan or by using the report RVFPLA01. You should schedule the report to run at regular intervals because new dates are not compiled automatically when you bill individual settlement periods. You can use the billing dates to determine when and how often billing is carried out, for example, on the first day or the last day of every month.
Which of the following is true with regard to milestone and periodic billing? You maintain the date proposal for periodic billing. You can enter as many dates per billing plan as you require. Dates that have already been billed can no longer be changed in the billing plan. You can display existing billing documents using the document flow. When you create a billing document, the system updates the status of the billing plan dates.
You will need to determine the accounts to be posted in several different areas as follows: When data is transferred from the billing document to Financial Accounting, general ledger (G/L) accounts for posting sales revenue, sales deductions, and value-added tax (VAT) are determined automatically. When processing cash sales, you must set a G/L account in the document for cash settlement (no posting to customer account). The system can determine a reconciliation account that is different from the account that is entered in the payer master record. When using payment cards, you also need to post to different G/L accounts.
Account Assignment Criteria in Billing Chart of accounts Sales organization Customer Account Assignment Group Material account assignment group Account key.
You can change the following data before an accounting document is created: Billing date Pricing Account determination Output determination data.
General Billing Interface. When you are using the general billing interface, you can invoice external documents in the SAP system (that is, orders and deliveries not created in the SAP system).To do this, you must do the following: Prepare the data in a sequential file of specified format. Specify a minimum number of required fields to be filled from the data records. Specify the remaining fields required for billing either through the data records for the sequential file or through the system (optional fields).
|
