BD6 S4HANA Credit Management

Test Script PUBLIC
SAP S/4HANA
November 2015
Credit Management(BD6_US)
Content
1 Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1 Purpose of the Document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.2 Purpose of Credit Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1 System Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.2 Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.3 Master Data, Organizational Data, and Other Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.4 Business Conditions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Preliminary Steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3 Overview Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
4 Testing the Process Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

4.1 Set a Credit Limit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
4.2 Sales Order Processing: Sale from Stock (optional). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
4.3 Sales of Nonstock Item with Order-Specific Procurement (optional). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
4.4 Make to Order Production w/o Variant Configuration (optional). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
4.5 Review Blocked Sales Orders - 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
4.6 Release or Reject Blocked Sales Orders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14
4.7 Review Blocked Sales Orders - 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
5 Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
5.1 Succeeding Processes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
PUBLIC Credit Management(BD6_US)

2 2015 SAP SE or an SAP affiliate company. All rights reserved. Content
1 Purpose
1.1 Purpose of the Document
This document provides a detailed procedure for testing the scope item after solution deployment, reflecting the predefined scope of the solution. Each process step is
covered in its own section, providing the system interactions (that is, test steps) in a table view. Steps that are not in scope of the process but are needed for testing are
marked accordingly (see column Test Step). Customer-project-specific steps must be added.
1.2 Purpose of Credit Management
A credit limit check can be carried out when sales documents are created or changed. The check is carried out by the system within one credit control area and one credit
segment. If you change quantities or values in a document, the check is repeated. A credit control area and credit segment consists of one or more company codes. A sales
document belongs to one credit control area and one credit segment depending on the allocation of the sales organization to a company code. The SAP System checks the
credit limit that was granted to the customer in this credit segment. The credit segments and the credit limit of a customer are defined in financial accounting and entered in
the customer master record. During the check, the SAP System totals the receivables, the open items and the net value of the sales order for every item of a sales document.
The open items take into account obligations bound by contract that are not recorded for accounting purposes but involve expenses through diverse business transactions.
After that, it compares the total with the credit limit. If the limit is exceeded, the system responds in the way defined by you in the configuration menu.
We are using automatic credit control in this solution. During the automatic credit control, you can configure a system reaction ('A' warning, 'B' error, 'C' like A, + value by
which the credit limit is exceeded. and D - like B, + value by which the credit limit is exceeded) when the credit limit is exceeded, we have chosen to use option C (warning +
value by which the credit limit is exceeded).
The system provides a transaction to list all sales documents that have been blocked for delivery, with information about what has caused the block. The customers current
credit situation is manually reviewed by the credit department, and when the sales order is approved, the delivery block is removed from the sales order. You can jump directly
from the list to an individual document.
Credit Management(BD6_US) PUBLIC

Purpose 2015 SAP SE or an SAP affiliate company. All rights reserved. 3
2 Prerequisites
2.1 System Access
The test should be conducted with the following system and users:
Type of Data Details
System System Accessible via Fiori launchpad. Your system administrator pro
vides you with the URL to access the various apps assigned to
your role.
2.2 Roles
Use the following standard test users or assign roles to testers, respectively:
SAP S/4HANA, on premise edition
Business Role Business Role ID Log On
SAP_BR_CREDIT_CONTROLLER
Credit Controller Suggested sample user CREDITCONTR
Customer Master Specialist SAP_BR_BUPA_MASTER_SPECIALIST Suggested sample user CUSTMASTER
SAP_BR_CUST_MASTER_SPECIALIST
For more information about business roles, refer to Assigning business roles to a user in the Administration Guide for SAP S/4HANA Solution Implementation.
SAP S/4HANA, cloud edition
Business Catalog Role Name Business Catalog Role ID Log On
Credit Management - Credit Cases SAP_BC_FIN_CR_CASES_MC Suggested sample user CREDITCONTR representing the busi
ness role Credit Controller

4 2015 SAP SE or an SAP affiliate company. All rights reserved. Prerequisites
Business Catalog Role Name Business Catalog Role ID Log On
Credit Management - Display Data SAP_FIN_BC_CR_DISP_DATA_MC Suggested sample user CREDITCONTR representing the busi
Credit Management - Manage Credit Accounts SAP_FIN_BC_CR_CREDIT_ACC_MC Suggested sample user CREDITCONTR representing the busi
Customer Master Specialist SAP_BCR_SD_CUST_MANAGE Suggested sample user CUSTMASTER representing the busi
ness role Customer Master Specialist
2.3 Master Data, Organizational Data, and Other Data
The organizational structure and master data of your company has been created in your system during activation. The organizational structure reflects the structure of your
company. The master data represents materials, customers, and vendors, for example, depending on the operational focus of your company.
Use your own master data or the following sample data to go through the test procedure.
Data Sample Value Details Comments
Customer 17100005
Company Code 1710
Credit Control Area A000
Credit Segment 1000
Sales organization 1710
Distribution channel 10
Division 00

Prerequisites 2015 SAP SE or an SAP affiliate company. All rights reserved. 5
2.4 Business Conditions
Before this scope item can be tested, the following business conditions must be met.
Business Condition Comment
1 To run through this scope item, the materials must be available You can create stock using the Manage Stock or Transfer Stock
apps
in stock.
Sales Order Processing: Sell from Stock (BD9)
2.4.1 Preliminary Steps
To run through this scope item, the materials must be available in stock.
Sales Order Processing: Sale from Stock (BD9)
Procedure
Complete all activities regarding Preliminary Steps described in the scope item: Sales Order to Cash: Sale from Stock (BD9).

6 2015 SAP SE or an SAP affiliate company. All rights reserved. Prerequisites
3 Overview Table
Process Step Business Role Transaction Expected Results
Set a Credit Limit [page 8] Customer Master Specialist BP Credit limit set
Sales Order Processing Sale from Stock [page See test script no. BD9 and/or J00 See test script no. BD9 and/or J00 See test script no. BD9 and/or J00
10]
Sales of Nonstock Item with Order-specific See test script no. BDN See test script no. BDN See test script no. BDN
Procurement (optional) [page 11]
Make to Order Production w/o Variant Config See test script no. BJE See test script no. BJE See test script no. BJE
uration (optional) [page 12]
Review Blocked Sales Order - 1 [page 13] Credit Controller UKM_Case Sales order is reviewed.
Release or Reject Blocked Sales Orders [page Credit Controller UKM_Case Sales order is released or rejected.
14]
Review Blocked Sales Orders - 2 [page 16] Credit Controller UKM_Case Blocked sales order are reviewed.
Follow-Up Processes (Optional):
Post-Processing Information (Sales Order See test script no. BD9 See test script no. BD9 See test script no. BD9
Processing)
Post-Processing Information (Sales Order See test script no. BDN See test script no. BDN See test script no. BDN
Processing)
Post-Processing Information (Sales Order See test script no. BJE See test script no. BJE See test script no. BJE
Processing)
Sales: Period End Closing Operations (BKK) See test script no. BKK See test script no. BKK See test script no. BKK

Overview Table 2015 SAP SE or an SAP affiliate company. All rights reserved. 7
4 Testing the Process Steps
4.1 Set a Credit Limit
Test Administration
Customer project: Fill in the project-specific parts.
Test Case ID <X.XX> Tester Name Testing Date Enter a test

date.
Business Role(s)
Responsibility <State Service Provider, Customer or Joint Service Duration Enter a

Provider and Customer> duration.
Context
In this activity, you set a credit limit for the customer.
Prerequisite
Business partner master record 17100005 is already created with credit management profile.

8 2015 SAP SE or an SAP affiliate company. All rights reserved. Testing the Process Steps
Procedure
Test Step # Test Step Name Instruction Expected Result Pass / Fail / Comment
1 Log onto SAP Fiori Launchpad Log onto the SAP Fiori Launchpad as The SAP Fiori Launchpad displays.
a Credit Controller.
2 Access the Fiori App Open Display Credit Master Data and The Master Data List displays.
choose the Execute button.
3 Select Customer Select the Customer row to process, The Display Organization:
and choose the Business Partner 17100005 role SAP Credit
Master Record button (Shift+F2). Management screen displays.
Partner: 17100005
4 Edit Choose the Switch Between Display The Change Organization:

and Change button (F6).
17100005 role SAP Credit
Management screen displays.
5 Credit Profile Select the Credit Profile tab and en

ter or review that the following infor
mation in the Scoring section exists.
Change in BP role: SAP Credit

Management (Maintained)
Rules: Standard rule with

no automatic calculation
Risk Class: Medium Default

Risk
Check Rule: Default - All

Checks Active
6 Credit Segment Choose the Credit Segment Data but

ton (Ctrl+F2). Check or enter the fol
lowing values in the Credit Segment
field:
Credit Segment: SAG AG

Testing the Process Steps 2015 SAP SE or an SAP affiliate company. All rights reserved. 9
7 Credit Limit In the Credit Limit section, select the Amount and validity date for credit
limit is set.
Limit Defined checkbox, and enter
the following values:
Limit: 5
Valid To: <End of Year>
8 Save Choose the Savebutton and choose Changes have been saved.
the Exit button to go back.
4.2 Sales Order Processing: Sale from Stock (optional)
Test Administration

date.
Business Role(s)

Context
This test script describes the entire process sequence for a standard sales process (sale from stock) with a customer.

Prerequisites
Sales order with customer 17100005must be created.
Procedure
Complete all activities regarding the creation of a sales order using the master data from the test script Sales Order Processing: Sale from Stock (BD9)and/orOrder to Cash:
Sell from Stock (J00).
4.3 Sales of Nonstock Item with Order-Specific Procurement (optional)
Test Administration

date.
Business Role(s)

Context
In this test script, a customer orders a material that is currently not in stock. The material is therefore procured from an external supplier.
Prerequisites
Sales order with customer 17100005 must be created.

Procedure
Complete all activities regarding the creation of a sales order using the master data from the Sales of Nonstock Item with Order-Specific Procurement (BDN) test script.
4.4 Make to Order Production w/o Variant Configuration (optional)
Test Administration

date.
Business Role(s)

Context
This test script describes the entire process sequence for a standard sales process (Make-to-Order) with a customer.
Prerequisites
Sales order with customer 17100005 must be created.
Procedure
Complete all activities regarding the creation of a sales order using the master data from the Make to Order Production w/o Variant Configuration (BJE) test script.
4.5 Review Blocked Sales Orders - 1
Test Administration

date.
Business Role(s)

Context
The sales order failed the credit check. In this activity, you review blocked sales orders and resolve any credit issues.
Prerequisites
Sales orders exceeding the Credit Limit settings are blocked due to credit check block.
Procedure
1 Log onto SAP Fiori Launchpad Log onto the SAP Fiori Launchpad The SAP Fiori Launchpad displays.
using as a Credit Controller.

2 Access the App Open Manage Credit Cases. The SAP Credit Management screen
displays.
If the Change to a Different RMS
screen pops up, select
UKM_CREDIT_CASE and choose
Continue.
3 Search Open SAP Credit Management Case Search displays, showing a list
of cases.
Cases and double-click
Documented Credit Decision -
Search. Choose the Search button.
4 Search Double-click a Case ID to process. The Case Display: Case

(3##########) (Documented
Credit Decision) is displayed.
5 Edit Choose the Display <-> Change but

ton to update data.
6 Change Update all the case fields as desired. Case data is changed.
Status: <In Processing>
Credit Analysis: <Your User>
Person Responsible: <Your User>
7 Save Choose Save. Changes have been saved.
4.6 Release or Reject Blocked Sales Orders
Test Administration

date.
Business Role(s)

Context
The sales order failed the credit check. In this activity, you release or reject blocked sales orders and resolve any credit issues.
Prerequisites
Procedure
1 Log onto SAP Fiori Launchpad Log onto the SAP Fiori Launchpad The SAP Fiori Launchpad displays.
using as a Credit Controller.
2 Access the App Open Manage Credit Cases. The SAP Credit Management screen
displays.
3 Search Open SAP Credit Management -- Case Search displays, showing a list
of cases.
Credit Case Cases and double-
click Documented Credit Decision -
Search. Choose the Search button.
4 Release Select the Case ID row to process.

The Ext. ref. column identifies the PO
number in a sales order.

5 Choose the Release button and in the The Sales Order is released and the
Display logs pop-up screen is shown.
Confirmation Prompt pop-up screen
Status of Case ID changes to Closed
choose Yes.
Automatically.
6 Reject Repeat step 3. Double-click Case ID The Case Display: Case

to process. (3##########) (Documented
Credit Decision) screen is displayed.
7 Choose the Display <-> Change but

ton to be to update data.
8 At the bottom section of the screen,

select Reason for Rejection and type
a note explaining the rejection.
9 In the top section select Sales A Reason for Rejection pop-up

Document > Reject and in the Reject screen is displayed.
Sales Document screen, choose Yes.
10 In the Reason for Rejection pop-up The Sales order is rejected and the
screen, select a rejection reason Display logs pop-up screen is shown.
code and choose Continue. Status of Case ID changes to Closed
Automatically.
Rejection reason: 61
4.7 Review Blocked Sales Orders - 2
Test Administration

date.

Business Role(s)

Use
The sales order failed the credit check. In this activity, you review blocked sales orders and resolve any credit issues.
Prerequisites
Procedure
Repeat same steps as in Review Blocked Sales Orders - 1 [page 13].

5 Appendix
5.1 Succeeding Processes
After completing the activities in this test script, you can continue testing the following test scripts:
Process Business Condition
Sales Order Processing: Sale from Stock (BD9) (optional) Entire process sequence for a standard sales process (sale from stock) with a customer.
Using the master data from this document, complete the following activities described in the
test script:
Process Sales Order: Sale from Stock
Sales of Nonstock Item with Order-specific Procurement (BDN) (optional) Customer orders a material that is currently not in stock. The material is procured from an ex
ternal supplier.
test script:
Sales of Nonstock Item with Order-specific Procurement
Make to Order Production w/o Variant Configuration (BJE) (optional) Entire process sequence for a standard sales process (sale from stock) with a customer.
test script:
Make to Order Production w/o Variant Configuration
Sales: Period End Closing Operations (BKK) (optional) Collection of periodic activities such as day ending activities or legal requirements like Intrastat
and Extrastat reporting.
test script:
Sales: Period End Closing Operations (BKK) (Review Blocked Sales Orders section)

18 2015 SAP SE or an SAP affiliate company. All rights reserved. Appendix
Important Disclaimers and Legal Information
Coding Samples
Any software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system environment. The Code is only intended to better explain and visualize the syntax and phrasing
rules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, unless damages were caused by SAP intentionally or by SAP's gross
negligence.
Accessibility
The information contained in the SAP documentation represents SAP's current view of accessibility criteria as of the date of publication; it is in no way intended to be a binding guideline on how to ensure accessibility of software products. SAP in particular
disclaims any liability in relation to this document. This disclaimer, however, does not apply in cases of wilful misconduct or gross negligence of SAP. Furthermore, this document does not result in any direct or indirect contractual obligations of SAP.
Gender-Neutral Language
As far as possible, SAP documentation is gender neutral. Depending on the context, the reader is addressed directly with "you", or a gender-neutral noun (such as "sales person" or "working days") is used. If when referring to members of both sexes, however, the
third-person singular cannot be avoided or a gender-neutral noun does not exist, SAP reserves the right to use the masculine form of the noun and pronoun. This is to ensure that the documentation remains comprehensible.
Internet Hyperlinks
The SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint about where to find related information. SAP does not warrant the availability and correctness of this related information or the ability of this
information to serve a particular purpose. SAP shall not be liable for any damages caused by the use of related information unless damages have been caused by SAP's gross negligence or willful misconduct. All links are categorized for transparency (see: http://
help.sap.com/disclaimer).

Important Disclaimers and Legal Information 2015 SAP SE or an SAP affiliate company. All rights reserved. 19
www.sap.com/contactsap
2015 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any
form or for any purpose without the express permission of SAP SE
or an SAP affiliate company. The information contained herein may
be changed without prior notice.
Some software products marketed by SAP SE and its distributors
contain proprietary software components of other software
vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company
for informational purposes only, without representation or warranty
of any kind, and SAP or its affiliated companies shall not be liable for
errors or omissions with respect to the materials. The only
warranties for SAP or SAP affiliate company products and services
are those that are set forth in the express warranty statements
accompanying such products and services, if any. Nothing herein
should be construed as constituting an additional warranty.
SAP and other SAP products and services mentioned herein as well
as their respective logos are trademarks or registered trademarks
of SAP SE (or an SAP affiliate company) in Germany and other
countries. All other product and service names mentioned are the
trademarks of their respective companies.
Please see http://www.sap.com/corporate-en/legal/copyright/
index.epx for additional trademark information and notices.

BD6 S4HANA Credit Management

Uploaded by

Copyright:

Available Formats

BD6 S4HANA Credit Management

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

BD6 S4HANA Credit Management

Uploaded by

Copyright:

Available Formats

What is the purpose of the document?

What is the purpose of the document?

What are the prerequisites for using the credit management system?

What are the prerequisites for using the credit management system?

Test Script PUBLIC

4 Testing the Process Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

PUBLIC Credit Management(BD6_US)

1.1 Purpose of the Document

1.2 Purpose of Credit Management

Credit Management(BD6_US) PUBLIC

2.1 System Access

Type of Data Details

SAP S/4HANA, on premise edition

Business Role Business Role ID Log On

Customer Master Specialist SAP_BR_BUPA_MASTER_SPECIALIST Suggested sample user CUSTMASTER

SAP S/4HANA, cloud edition

Business Catalog Role Name Business Catalog Role ID Log On

PUBLIC Credit Management(BD6_US)

2.3 Master Data, Organizational Data, and Other Data

Data Sample Value Details Comments

Company Code 1710

Credit Control Area A000

Credit Segment 1000

Sales organization 1710

Credit Management(BD6_US) PUBLIC

Business Condition Comment

Sales Order Processing: Sell from Stock (BD9)

2.4.1 Preliminary Steps

Sales Order Processing: Sale from Stock (BD9)

PUBLIC Credit Management(BD6_US)

Process Step Business Role Transaction Expected Results

Follow-Up Processes (Optional):

Credit Management(BD6_US) PUBLIC

4.1 Set a Credit Limit

Customer project: Fill in the project-specific parts.

Test Case ID <X.XX> Tester Name Testing Date Enter a test

Responsibility <State Service Provider, Customer or Joint Service Duration Enter a

In this activity, you set a credit limit for the customer.

PUBLIC Credit Management(BD6_US)

4 Edit Choose the Switch Between Display The Change Organization:

5 Credit Profile Select the Credit Profile tab and en

Change in BP role: SAP Credit

Rules: Standard rule with

Risk Class: Medium Default

Check Rule: Default - All

6 Credit Segment Choose the Credit Segment Data but

Credit Segment: SAG AG

Credit Management(BD6_US) PUBLIC

Valid To: <End of Year>

4.2 Sales Order Processing: Sale from Stock (optional)

Customer project: Fill in the project-specific parts.

Test Case ID <X.XX> Tester Name Testing Date Enter a test

Responsibility <State Service Provider, Customer or Joint Service Duration Enter a

PUBLIC Credit Management(BD6_US)

Sales order with customer 17100005must be created.

4.3 Sales of Nonstock Item with Order-Specific Procurement (optional)

Customer project: Fill in the project-specific parts.

Test Case ID <X.XX> Tester Name Testing Date Enter a test

Responsibility <State Service Provider, Customer or Joint Service Duration Enter a

Sales order with customer 17100005 must be created.