SAP ABAP IMG Activity VC_TFDM_SOURCEFIELDS (Define Document Changes)
Hierarchy
☛ SAP_FIN (Software Component) SAP_FIN
   ⤷ FIN-FSCM-DM-AR (Application Component) Accounts Receivable Accounting Process Integration
     ⤷ FDM_AR_CUSTOMIZING (Package) FSCM Dispute Management Process Integrtn - FI-AR Customizing
IMG Activity
ID VC_TFDM_SOURCEFIELDS Define Document Changes  
Transaction Code S_PR0_40000305   (empty) 
Created on 20061221    
Customizing Attributes VC_TFDM_SOURCEFIELDS   Define Document Changes 
Customizing Activity VC_TFDM_SOURCEFIELDS   Define Document Changes 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name VC_TFDM_SOURCEFIELDS    

Use

With the Automatic Document Changes from Dispute Cases function, you can control that when you create or change a dispute case, certain attributes are changed automatically in the related FI documents (for example, a dunning block could be set).

In this activity, you specify which fields in the FI documents are changed when the triggering attributes in the dispute case change.

Requirements

You have already specified which fields in the dispute case trigger document changes under Define Triggering Attributes for Document Changes.

You find this Customizing activity in the IMG structure Dispute Case Processing for SAP Dispute Management under Financial Supply Chain Management -> Dispute Management -> Dispute Case Processing -> Process Integration -> Automatic Document Changes from Dispute Cases -> Define Triggering Attributes for Document Changes.

Standard settings

Activities

  1. Create a new entry for the corresponding Company Code and the desired Case Type and save your entry.
  2. Select this entry and choose the next level Selection of Fields.
  3. Choose the Target Field that is to be automatically changed in the FI document.

    The following fields are available:

  4. Choose up to 5 origin fields from the dispute case that are relevant for this change.

    The only fields available to you for this are those you selected under Define Triggering Attributes for Document Changes.

    Start making entries for origin fields at OriginField1 and then complete the other origin fields in ascending order, making sure you do not leave any entry initial.

  5. If you allow manual changes using the indicator Allow Manual Changes, set the indicator System Value Can Overwrite Manual Changes if required.
  6. Set the indicator Allow Manual Changes if required.

    Note: You should be aware that not all combinations of the two indicators are meaningful and some combinations can give unwanted results.

  7. Save your entries and choose the next level Determination of Field Values.
  8. Now choose individual field values or combinations of field values for the origin fields and the corresponding value to be set in the target field.

    When you do this, make sure that you enter specified entries first and then unspecified entries. In other words, if you want, for example, a specified entry in the target field for a particular value in the origin field and a different entry for the other values, define the entry for this particular value first and then the unspecified entry for the other values in the origin field. This is because an initial entry for a field value means that all values in the field are taken into account and not just the initial value. The system can only process masking like this correctly if the fields with specified values are entered first. This is also important for the sequence of origin fields.

    Make sure that you define an entry for every value in the origin fields including if the field value is set to 'initial'.

  9. If you want to carry out the change in the future, enter in how many days' time.
  10. Save your entries.

Further notes

  • Make sure that an attribute is not reset automatically to initial but must be set explicitly.

    This means that if during the dispute case term an origin field is set to 'initial', the target field in the document is only changed if you have defined an entry in this Customizing activity for when an origin field = 'initial'.

  • If a dispute case is confirmed or voided, the attributes in the FI documents are automatically reset to their original value.

    Exception:

    If a document change performed using the function Document Changes from Dispute Cases is later changed manually, the system can no longer determine the original field value when it confirms or voids the dispute case. The field can only be reset to the value that was manually set. If this happens, you must correct the field manually if necessary using the document change transaction.

Example

You want the change of the attribute 'Category' in a dispute case with the case type 'F_DM' in company code '0001' to the value 'Category A' to set a dunning block 'A' in the FI documents disputed.

  1. Choose New Entry in the Overview:

    Enter company code '0001' and case type 'F_DM' (or choose the entry in the F4 help input).

  2. Save your entry.
  3. Select this entry and choose the next level Selection of Fields.
  4. Choose 'Dunning Block' as the target field.
  5. Choose 'Category' as the origin field.
  6. Save your entry.
  7. Select this entry and choose the next level Determination of Field Values.
  8. Choose the category 'Category A'.
  9. Choose 'A' as dunning block.
  10. Save your entry.

Further notes

See also the documentation for the Document Changes from Dispute Cases function in the SAP Library under SAP Dispute Management for FI-AR (FIN-FSCM-DM) -> Process Integration with Accounts Receivable Accounting -> Document Changes from Dispute Cases.

Business Attributes
ASAP Roadmap ID 204   Establish Functions and Processes 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG VC_TFDM_SOURCEFIELDS 0 XBI0000001 Accounts Receivable Accounting Process Integration 
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
VC_TFDM_SOURCEFIELDS C - View cluster SM34  
History
Last changed by/on SAP  20061221 
SAP Release Created in 700