“Customer Statement Generation” Program has its own pros and cons. Some client implement it and other ignored it but it is one of good features to use. Many time we get performance or data issues and need to troubleshoot, here are some step to identify any problems :

Enable “Debug Flag” at program level

Responsibility: System Administrator
Navigation: Concurrent > Program > Define
Query shortname = ARXSGP
Click Parameters
Scroll to parameter debug_flag

This might be the last parameter, seeded value for default = select meaning from  fnd_lookups where lookup_type = ‘YES_NO’ and lookup_code = ‘N’

Change this to : select meaning from fnd_lookups where lookup_type = YES_NO’ and lookup_code = ‘Y’  and Save

Set Profile Option ( AR: Enable Debug Message Output ) as Yes

Responsibility: System Administrator
Navigation: Profile > System

Query for Application = Receivables
user = <your user name>
Profile Option = AR: Enable Debug Message Output – Ensure it is set to Yes.

Normally, the statement generation process creates data in the AR_STATEMENT* tables which are used for statement printing. After the statements process completes, it deletes data in these temporary tables. When you need to debug the behavior of statements, it is sometimes necessary to see the data that was populated into these tables. You can disable the deletion of records in the tables by doing the following.

Responsibility: Receivables Manager
Navigation: Print Documents > Statements

Invoke the Menu: Help > Diagnostic > Examine  –Enter the following values:

Value = Y
Click OK and Submit the program

Verfiy Log file :  Review the log file generated by the Concurrent Process: Statement Generation Program. If debug was enabled correctly, you should see text like the following in the log file.

  • arxsgp: Argument 38 Y
  • arxsgp: DEBUG_FLAG is Y, records in interim tables will NOT be deleted

The Statements program use the following 2 interim tables to generate the statement:
The AR_STATEMENT_HEADERS and AR_STATEMENT_LINE_CLUSTERS are interim tables populated by the Statement Generation program. The code creates rows in these tables that are then picked up by the Print Statements program. You can  check the data in following tables:
Picture of AR - Statement Printing (3:45)

One thought

  1. hi,
    If we execute Statement Generation Program with deubg option Yes then it brings data if debug option is either NULL or N then it is not bringing the data, please share what could be the cause


Want to give some comment to author ( Shivmohan Purohit )

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s