Convergent Invoicing: Clarification Lists This post is on the creation of Clarification cases in Convergent Invoicing. Below I am

just presenting a snapshot, more on this can be found here.

I have just done one use case for clarification case category 01 – Source Documents

which is shown below the minimal text I have copy pasted here from the help link of

SAP CI.

Situations can arise during the processing of billing documents and during invoice

creation, where we need to clarify exceptional situations and process them. This can be

an automated process or manual and assigned to an agent for post processing.

• This is an application of the Clarification Framework Controller (CFC) and called using

transaction FKKINV_CFC.

• Validation checks are necessary to decide whether clarification is needed or not. The

elements which are checked are Source documents (clarification case category 01),

Invoicing Documents (clarification case category 03), Contract Accounts (clarification

case category 04) and Error Messages (clarification case category 06). We can create

and apply our own validation rules. We can have multiple checks and can define the

sequence in which the checks are to be run when we assign them.

• The checks are processed at various levels like during transfer of billing documents or

during billing execution, checking the invoicing order and during invoicing. It is not

possible to invoice the source documents or the contract account until these cases have

been clarified, either automatically or manually.

• Billing documents are source documents of the source document category INVBI that

were created in Billing.

• For check module (Source documents) Function module FKK_SAMPLE_TFK2672

from function group FKKINV_EVENT is available as a sample module.

http://wp.me/p1Ci5j-gN www.sapisurdg.wordpress.com

• For check module (Invoicing Documents) Function module FKK_SAMPLE_TFK2671

from function group FKKINV_EVENT is available as a sample module. The checked

invoicing document is marked as a control document for the clarification case in the

invoicing document header. This is a simulation document, since no postings are made

in Contract Accounts Receivable and Payable.

• A control document, documents the exception situation that led to the creation of the

clarification case in Invoicing. It provides the user processing the clarification case with

information on the composition of the invoicing unit. After clarification, the control

document is no longer needed. After the clarification case has been deleted, the

document can be deleted together with other simulated documents.

• The invoicing lock reason specified in the master record for the contract account

determines whether invoice clarification is triggered in invoicing for the contract

account. If the lock reason is marked in its definition as “To Be Clarified” and is assigned

a clarification reason, a clarification case can be created in invoicing for the contract

account if the document date used is in the validity period of the invoicing lock. If there

is a lock reason without clarification information, the invoicing lock in the contract

account prevents invoicing from taking place but the system does not create a

clarification case.

• We can create an exception list for messages, by assigning one or more messages

(message class and message number) that trigger a clarification case to the invoicing

process and optionally to the invoicing type and invoicing category. We can enter a

clarification reason for the message in posting area 2673.

• Clarified cases with a contract account reference (clarification case categories 03 to 06)

do not influence validation in the invoicing process, irrespective of whether they were

clarified automatically or manually. However clarified cases with reference to a source

document (clarification case categories 01 and 02) are taken into account: in this case,

the system does not check the source document again during the invoicing process.

http://wp.me/p1Ci5j-gN www.sapisurdg.wordpress.com

• Unlike validation in the invoicing process, validation in the billing process validates

billing documents. These documents are created in billing. From an invoicing point of

view, they represent source documents.

• There are two types of billing process. These are simulated billing and actual billing.

For simulated billing, the system does not create any clarification cases, even if a billing

document does not pass a check. To enable one to understand why checks have failed

without the use of a clarification case, the system writes messages to the application log

during billing simulation. For actual billing, the system creates clarification cases. It

does not write messages to the application log. However, the application log informs you

that a clarification case was created.

• If we reverse a billing document, the system automatically closes any existing

clarification cases. The system can then only create new clarification cases for the billing

document during a new billing run.

• Every clarification case is uniquely assigned to one contract account.

• A clarification case is classified by a clarification case category.

• Clarification cases with clarification case category 01 or 02 relate to a source

document.

• Clarification cases with clarification case type 03, 04, 05 or 06 do not refer to a source

document.

• A source document can have a maximum of one clarification case with clarification

case category 01.

• It is not possible to assign a clarification case to an invoicing document. An invoicing

document can be checked at runtime. If it is found to be implausible then a clarification

case can be created with clarification case type 03. The invoicing is then ended early and

the invoicing document is not created.

• The clarification case contains status information. The clarification case can have the

following statuses during clarification processing:

o New

o Clarify

http://wp.me/p1Ci5j-gN www.sapisurdg.wordpress.com

o In process

o Completed

Below are the Clarification Case Categories.

Below I am setting up the validation for ‘Check source Documents’.

http://wp.me/p1Ci5j-gN www.sapisurdg.wordpress.com

Now the Amount Limit values is been set up. There are 3 limits which can set up, I am

working with the first one for now.

http://wp.me/p1Ci5j-gN www.sapisurdg.wordpress.com

Execution of the Billing is shown below.

http://wp.me/p1Ci5j-gN www.sapisurdg.wordpress.com

The clarification case check is triggered as shown below.

http://wp.me/p1Ci5j-gN www.sapisurdg.wordpress.com

The clarification case created is shown when I press the ‘New clarification Case’ button

in the previous screen.

http://wp.me/p1Ci5j-gN www.sapisurdg.wordpress.com

Looking into the details of the clarification case that was created above.

http://wp.me/p1Ci5j-gN www.sapisurdg.wordpress.com

The work list looks like this for the agent.

http://wp.me/p1Ci5j-gN www.sapisurdg.wordpress.com

Once the clarification process is triggered by the agent the status of the document

changes as shown below.

http://wp.me/p1Ci5j-gN www.sapisurdg.wordpress.com

Once the case has been clarified the status is updated to ‘completed’ as shown in the

work list.

Clarification case can be created manually as shown below.

http://wp.me/p1Ci5j-gN www.sapisurdg.wordpress.com

The clarification case is in status ‘new’ as created manually.

http://wp.me/p1Ci5j-gN www.sapisurdg.wordpress.com

Once saved it and processing has been triggered by the agent.

Thanks :)

http://wp.me/p1Ci5j-gN www.sapisurdg.wordpress.com