SAP ABAP Data Element CUST_DOC_KK (Invoicing Function: Create Customer Documents)
Hierarchy
☛ FI-CA (Software Component) FI-CA
   ⤷ FI-CA-INV (Application Component) Invoicing to Contract Accounts Receivable and Payable
     ⤷ FKKINV (Package) Invoicing in Contract Accounts Receivable and Payable
Basic Data
Data Element CUST_DOC_KK
Short Description Invoicing Function: Create Customer Documents  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type CHAR12    
Data Type CHAR   Character String 
Length 12    
Decimal Places 0    
Output Length 12    
Value Table      
Further Characteristics
Search Help: Name    
Search Help: Parameters    
Parameter ID   
Default Component name    
Change document    
No Input History    
Basic direction is set to LTR    
No BIDI Filtering    
Field Label
  Length  Field Label  
Short 10 Cust. Docs 
Medium 15 Customer Docs 
Long 20 Customer Documents 
Heading 31 Creation of Customer Documents 
Documentation

Definition

You only have to activate the function for creating customer own documents if the relevant event is defined in a customer implementation and documents (customer documents) are posted there with invoicing.

Dependencies

The function must be either activated or deactivated for all invoicing processes defined. If this is not the case, there is a danger that customer documents are not always posted when expected.

If customer documents are posted in invoicing, a corresponding customer function for invoicing reversal must be defined in an event in the invoicing reversal in order to enable customer documents posted with invoicing also to be reversed with this invoicing.

See the following in the programming of database changes in events:

Programming Restrictions

To ensure the consistency of the system, note that you must not use the following language elements in events:

  • COMMIT WORK
  • ROLLBACK WORK
  • CALL FUNCTION 'DEQUEUE ALL'
  • Deletion of locks that you have not set yourself.

If you update additional data in an event and use the construction PERFORM commitroutine ON COMMIT to do this, note that:

  • At the end of the commitroutine, all internal tables from which data was updated must be initialized again to prevent a duplicate update in the next call.
  • A PERFORM rollbacktroutine ON ROLLBACK must also be called. In the rollbackroutine initialize the same data that is initialized at the end of the commitroutine.

If you want to carry out checks in an event, when you issue messages, note that background processing of the process terminates with warning messages. You should therefore avoid issuing warning messages if possible. However, you should definitely issue warning messages if the value of SY-BATCH is initial.

Example

History
Last changed by/on SAP  20070914 
SAP Release Created in 600