When an Incoming Payment is added, SAP Business One first checks that at least one payment means (cash, cheque, bank transfer, credit card, etc.) has been entered. It then verifies that the total entered in the Payment Means window equals the payment amount that results from the invoices selected. If either control fails, the system blocks posting and raises the message shown in the screenshot.

C. Exchange-rate control is performed when the foreign-currency invoice is created; an Incoming Payment posts as long as the day’s rate exists, otherwise a specific “Exchange rate is missing” error appears.

D. SAP Business One allows invoices to be paid before due date; due status is informational only and does not prevent posting.

1. SAP Business One 10.0 Financials / Banking Documentation

section “Incoming Payments – Payment Means”

pp. 491-492: “Payment cannot be added unless at least one payment means exists and the total of payment means equals the payment amount.”

2. SAP Learning Hub course TB1200 (SAP Business One – Logistics & Accounting)

Unit “Manual Incoming Payments”

Lesson “Posting Rules”

slide 14: validation of payment means presence and total equality prior to Add.

3. SAP Help Portal

SAP Business One 10.0 → Banking → Incoming Payments

“Prerequisites” paragraph 3 (Doc ID SBC100FINIPAY10): payment means required; total must match document total.

Profit and Loss (P&L) accounts, also known as nominal or temporary accounts, are used to record revenues and expenses for a specific accounting period. A fundamental principle of accounting requires that at the end of each fiscal year, the balances of all P&L accounts are transferred to a balance sheet equity account, typically "Retained Earnings." This process, known as period-end closing, effectively resets or clears the P&L account balances to zero, preparing them to accumulate data for the new fiscal year.

A. Balance sheet accounts (Assets, Liabilities, Equity) have their balances carried forward to the next fiscal year; this is the defining characteristic of a permanent account, not a P&L account.

B. A cash account is a specific type of balance sheet account used for recording cash transactions. P&L accounts, such as 'Sales Revenue' or 'Rent Expense', are not cash accounts.

D. In the standard SAP Business One chart of accounts, the first three drawers are reserved for balance sheet accounts (Assets, Liabilities, and Equity). P&L accounts are located in subsequent drawers.

1. SAP Business One 10.0 Help Portal

"Period-End Closing": "The period-end closing utility transfers the balances of all P&L accounts to a balance sheet account that you define

for example

a retained earnings account. As a result

all P&L accounts have a zero balance at the beginning of the new posting period." (This directly supports answer C and refutes A).

2. SAP Business One 10.0 Help Portal

"Chart of Accounts Window": "The chart of accounts is structured like a chest of drawers... The first three drawers contain the G/L accounts for assets

liabilities

and equity... The other five drawers contain the G/L accounts for revenues

cost of sales

expenses

financing

and other revenues and expenses (or non-operating income and expenditure)." (This directly refutes answer D).

3. SAP Press

Financial Accounting with SAP S/4HANA (While for S/4HANA

the core accounting principle is identical and universally applicable to SAP ERP systems including Business One): "At the end of the fiscal year

the balances of the P&L statement accounts are set to zero... The net profit or loss for the year is calculated from the balances of the P&L statement accounts. This net profit or loss is then posted to an equity account (retained earnings)." (Chapter 3

Section 3.2.2

G/L Accounts). This confirms the fundamental accounting principle behind answer C.

The Remote Support Platform (RSP) for SAP Business One is the designated tool for support consultants to manage system health and facilitate support processes. It includes a specific function to automate the transfer of a customer database to SAP support. This process involves creating a backup, compressing and encrypting the file, and securely uploading it to SAP's servers, automatically linking it to an existing support incident. This ensures a secure, efficient, and standardized method for providing necessary data for analysis by SAP's support team.

A. Support Launchpad: This is the central web portal for creating and managing support incidents, but it is not the tool that performs the actual database file transfer.

B. System Landscape Directory: The SLD is a central repository for system landscape information and is used for managing system connections, not for transferring databases for support cases.

C. System Data Maintenance: This is a generic term for managing system-level data and not a specific, named tool used for transferring databases to SAP support.

1. SAP Help Portal

Administrator's Guide for Remote Support Platform 3.2 for SAP Business One

Section 5.3 "Sending a Database to SAP Support": "You can send a customer database to SAP support for analysis. The remote support platform for SAP Business One automates the process of backing up the database

compressing the backup file

and uploading it to a secure SAP server."

2. SAP Business One 10.0

TB1200 Training Manual

Unit 8: Support Processes

Lesson: Remote Support Platform: This course material details the functions of the RSP

explicitly mentioning its capability to "Send database to SAP Support" as a key feature for partners to resolve customer issues with SAP's assistance. The tool is presented as the primary mechanism for this task.

In SAP Business One, business partners are categorized as leads, customers, or vendors. A 'lead' is used for pre-sales activities, such as creating a sales quotation. However, logistical and accounting documents like a delivery or an A/R invoice can only be created for a 'customer'. Therefore, once a lead accepts a quotation, the mandatory first step is to convert the lead master data into a customer master data record. This action transfers all associated data and documents, including the accepted sales quotation, to the new customer record, enabling the creation of subsequent documents in the sales process.

A. Copy the sales quotation to a sales order: This action is impossible while the business partner is still a lead. The system requires a customer record to create a sales order.

C. Change the status of the sales quotation: Changing a document's status (e.g., to 'Closed') is for reporting and process tracking; it does not change the underlying system requirement that a delivery needs a customer.

D. Perform an availability check: An availability check confirms stock levels, which is a crucial business step, but the system will not even allow the creation of a delivery document for a lead, regardless of item availability.

1. SAP Business One 10.0

TB1200 Logistics

Unit 4: Sales Process

Section: The Sales Process.

This official SAP training material outlines the end-to-end sales process. It explicitly states that after a sales quotation is created for a lead and accepted

the lead must be converted into a customer before a sales order or any subsequent delivery document can be processed. The system logic enforces this conversion as a prerequisite for moving from the pre-sales to the sales execution phase.

2. SAP Help Portal for SAP Business One

"Business Partner Master Data."

The documentation distinguishes between the three types of business partners. It specifies that "Leads are used to manage information about potential customers... To enter sales orders for a lead

you first have to convert it to a customer." This principle extends to all subsequent sales documents

including the delivery.

3. SAP Help Portal for SAP Business One

"Creating Business Partner Master Data from a Lead."

This section details the procedure for converting a lead. It notes

"You can convert a lead into a customer at any stage of the sales process. For example

after a lead has shown interest in your products

you can convert it into a customer and create a sales order for it." This confirms that conversion is the enabling step for creating sales orders and

by extension

deliveries.

The Opportunity is the central business object in SAP CRM designed to manage and track a potential sales deal through its entire lifecycle. It captures key information such as potential revenue, sales stage, and probability of closing. By aggregating all active opportunities, sales managers and representatives gain a clear and structured view of the sales pipeline. This visibility is crucial for sales forecasting, resource planning, and managing the overall sales process effectively.

A. Customer 360: This is a consolidated view that provides a holistic profile of a customer, aggregating data from all interactions, but it is not the transactional object that constitutes the sales pipeline.

C. Activity: An activity represents a single task or interaction, such as a phone call or a meeting. While activities are essential for progressing an opportunity, they do not represent the potential deal itself.

D. Campaign: This is a marketing object used to plan and execute marketing initiatives. A campaign's goal is often to generate leads, which may later become opportunities, but it does not manage the sales pipeline.

---

1. SAP Help Portal

SAP CRM 7.0 EHP4

"Opportunity Management": "An opportunity is a recognized possibility for a sale of products or services... You can use opportunities to control your sales process. The sales process is mapped in the system using sales stages... Sales Pipeline Analysis is one of the key features of Opportunity Management." (This document directly links the Opportunity object to sales process control and pipeline analysis).

2. SAP Help Portal

SAP Sales Cloud

"Opportunities Quick Guide": "An opportunity is a potential deal that you want to track through the sales cycle... Use opportunities to manage your sales pipeline and forecast revenue." (This confirms the role of the Opportunity object in modern SAP sales solutions for pipeline management).

3. SAP Training Course CTB120010

"SAP Certified Application Associate - SAP Business One Release 10.0" Syllabus: The "Sales - A/R" topic area explicitly covers the sales process

including the management of sales opportunities as the foundation for tracking potential deals from lead to closure

which is the definition of a sales pipeline. The Opportunity object is the core component of this process.

When an A/R invoice is posted based on a preceding delivery document in SAP Business One, it creates a journal entry to recognize the revenue and the customer's debt. The transaction debits the customer's control account (Accounts Receivable), increasing the amount owed to the company. Simultaneously, it credits the sales revenue account, which increases the company's income. The inventory and Cost of Goods Sold (COGS) accounts were already updated by the journal entry created from the delivery document.

B. A credit to cost of goods sold account

The Cost of Goods Sold account is debited (not credited) when the delivery document is posted, reflecting the cost of the items shipped.

D. A debit to a sales revenue account

A debit decreases a revenue account. Posting an invoice increases sales revenue, which is recorded as a credit in accounting.

1. SAP Business One TB1200ENCol10 Participant Handbook

Unit 5: Sales - A/R

Page 19.

The documentation states the journal entry for an A/R Invoice is: "Debit: Customer account; Credit: Revenue account." It also clarifies on page 17 that the journal entry for the preceding Delivery is: "Debit: Cost of Goods Sold account; Credit: Inventory account." This confirms the separation of the accounting postings.

2. SAP Help Portal for SAP Business One

"A/R Invoice - General Information".

The official documentation specifies the accounting impact: "When you add an A/R invoice

SAP Business One creates a journal entry that posts a debit to the customer account and a credit to the revenue account." This directly supports the correct answers.

The Customer 360 is a pre-defined, context-sensitive dashboard in SAP Business One, version for SAP HANA. It is officially classified as an "Advanced Dashboard." This type of dashboard provides a comprehensive, multi-faceted view of a single business object—in this case, a specific customer. It consolidates key information such as sales history, open documents, and fulfillment rates into one interactive screen, which is typically launched directly from the Business Partner Master Data window.

A. Pervasive Dashboard: Pervasive dashboards are general, system-wide dashboards displayed on the user's cockpit for a high-level business overview, not a detailed, specific view of a single customer.

B. SAP HANA app: This is a generic term. While Customer 360 leverages SAP HANA technology, "SAP HANA app" is not its specific classification within the SAP Business One analytical framework.

D. KPI: A Key Performance Indicator (KPI) is a widget that displays a single, specific metric (e.g., 'Total Sales Revenue'). Customer 360 is a collection of multiple charts and KPIs, not a single KPI itself.

1. SAP Business One 10.0 Administrator's Guide

version for SAP HANA

Document Version: 1.2 – 2020-06-15. In Chapter 4

"Analytics Powered by SAP HANA"

section 4.3.2 Advanced Dashboards

it explicitly states: "SAP Business One

version for SAP HANA provides two advanced dashboards: Customer 360° and Item 360°." (Page 51)

2. How to Work with Pervasive Analytics for SAP Business One 9.1

version for SAP HANA

Document Version: 1.1 – 2014-07-28. Section 3.3 Advanced Dashboards

describes the Customer 360 dashboard as an example of an advanced dashboard that provides a holistic view of a business object. (Page 15)

A Goods Receipt PO (GRPO) is the document in SAP Business One that records the physical receipt of goods into a warehouse. The primary and direct impact of posting a GRPO is the increase of the physical inventory count, which is reflected in the 'In-Stock' quantity field.

The 'Available' quantity (also known as Available-to-Promise or ATP) is a calculated value: Available = In-Stock - Committed + Ordered. Since this GRPO is created without a reference to a Purchase Order, the 'Ordered' quantity is not affected. The transaction increases the 'In-Stock' quantity, and with no change to the 'Committed' or 'Ordered' quantities, the 'Available' quantity consequently increases.

A. Increases the committed quantity

'Committed' quantity represents stock reserved for customers via open sales orders. A GRPO is an inbound purchasing transaction and does not affect customer commitments.

C. Decreases the ordered quantity

'Ordered' quantity is decreased only when a GRPO is created based on (i.e., by copying from) an open Purchase Order. The question explicitly states no PO is referenced.

1. SAP Business One 10.0 Help Portal - Goods Receipt PO Window:

Reference: In the section describing the functionality of the GRPO

it states

"Use this window to record goods that you receive from a vendor... When you create a goods receipt PO

SAP Business One receives the goods into the warehouse

and updates the quantities." This confirms the increase in 'In-Stock' quantity. The document also details the inventory effects of the transaction.

2. SAP Business One 10.0 Help Portal - General Tab: Item Master Data:

Reference: This document defines the inventory level fields. It specifies:

In Stock: "The current stock level of the item." A GRPO directly increases this.

Available: "The available quantity of an item... The calculation is based on the formula: In Stock Quantity + Ordered Quantity - Committed Quantity." This confirms that an increase in 'In-Stock' directly leads to an increase in 'Available' when other factors are constant.

3. SAP Training Course TB1200: SAP Business One - Logistics:

Reference: Unit 4: Purchasing – A/P

Lesson: Goods Receipt PO. This lesson explains that a GRPO is the key document for increasing inventory levels upon receipt of goods. It also clarifies that if a GRPO is not based on a PO

it is a standalone document that solely increases the 'In-Stock' quantity without affecting the 'Ordered' quantity.

This scenario requires a two-part solution: one for migrating existing historical documents and another for creating new documents post-go-live.

1. For existing legacy documents that need to be entered into SAP Business One (e.g., open A/R invoices), a manual numbering series is used. This allows the user to enter the exact, original document number from the legacy system, thus preserving the historical numbering without alteration.

2. For new documents created after the system goes live, a new automatic numbering series should be defined. The "Next Number" for this series must be set to the number immediately following the last used number in the legacy system. This ensures a seamless and continuous numbering sequence with no breaks.

C. Use the primary series with a prefix for the legacy numbers: This is incorrect because adding a prefix changes the document number, which violates the requirement to continue the exact legacy numbers.

D. Use the primary series and change the starting number: While technically possible, creating a new, dedicated series (Option B) is better practice than altering the default primary series, which may be needed for other standard purposes.

1. SAP Business One 10.0 Help Portal; Document Title: Document Numbering - Setup Window.

Reference Details: In the section describing the fields for setting up document numbering

the documentation implicitly supports the use of manual series for entering specific numbers and setting the "Next No." field for automatic series to control the sequence. This directly supports options A and B as the standard mechanism for this requirement.

2. SAP Business One TB120010 Course Material; Unit: System Initialization.

Reference Details: The "Document Numbering" topic within this unit explains the distinction between automatic and manual series. It outlines the best practice for data migration

which involves creating a manual series to import historical documents with their original numbers. It also details how to set up a new automatic series to continue a specific numbering sequence for ongoing operations

aligning perfectly with answers A and B.

The security level in the SAP Business One Cash Flow report indicates the certainty of a future cash flow event. The system automatically assigns a default security level to each transaction based on its origin or type. For example, a posted A/R invoice represents a legal obligation and is assigned a high security level (e.g., 'Confirmed'), whereas a sales order represents a future potential receivable and is assigned a lower security level (e.g., 'Probable'). This initial assignment is directly influenced by the type of source document, reflecting its stage in the business process.

A. The due date of the transaction: The due date determines when the cash flow is expected to occur in the report's timeline, not its level of certainty.

C. The payment terms of the transaction: Payment terms are used to calculate the due date of a transaction, which influences timing, but not the inherent security level.

D. The amount of the transaction: The amount defines the magnitude or value of the potential cash flow, not the probability or certainty of its occurrence.

1. SAP Business One 10.0 Help Portal: In the documentation for the "Cash Flow Forecast" window

under the "Certainty Level" field description

it is explained that the system proposes a certainty level for each transaction based on its origin. For instance

an open A/R invoice is considered more certain than a sales order. (SAP Business One 10.0 Documentation

Financials Module -> Financial Reports -> Cash Flow Forecast).

2. SAP Training Course TB1200 (SAP Business One - Logistics): Unit 8: Financials

in the section covering the Cash Flow Forecast

details how different source documents (transaction origins) like invoices

orders

and down payments are assigned different default certainty levels to reflect their varying degrees of commitment. (TB1200ENCOL10

Unit 8

Financials).