SAP ABAP IMG Activity SIMG_CFMENUORFBOB96 (Define Form Names for Correspondence Print)
Hierarchy
BBPCRM (Software Component) BBPCRM
   CRM-MD-BP (Application Component) Business Partners
     FB0C (Package) Financial Accounting customers
IMG Activity
ID SIMG_CFMENUORFBOB96 Define Form Names for Correspondence Print  
Transaction Code S_ALR_87003387   IMG Activity: SIMG_CFMENUORFBOB96 
Created on 19981222    
Customizing Attributes SIMG_CFMENUORFBOB96   Assign Form for Correspondence 
Customizing Activity SIMG_CFMENUORFBOB96   Assign Form for Correspondence 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SIMG_CFMENUORFBOB96    

In this activity, you define the names of the forms which are to be used for printing the correspondence.

The system attempts to create the letters for your customers/vendors in the language specified in the customer/vendor master record. Internal documents are issued in the company code or logon language. To do this, the corresponding form must be available in the required language in the system. You should therefore translate the forms into the required languages if they are not already available in the standard system.

You define the form names depending on the company code, print program and a form ID. With the help of the form ID, it is possible to store different forms for one print report.

Example

You want to create account statements with and without displaying the days in arrears. For this, you defined a correspondence type. For every account statement type you also create your own form and store the names of the forms for the print program "RFKORD10" under your own form ID.

If you want to use the form IDs, you should note that you must enter them in the selection variants for the print reports. You need the corresponding number of variants.

Example

You are to be able to create payment notices with and without an individual text. To do this, you store a form without form ID for the program RFKORD00. This form does not have any individual texts defined for it. You store another form under a form ID. This form does have an individual text defined for it. You create two selection variants for the print program and store these variants for the relevant correspondence types in the system.

Text elements are contained in the standard forms. Text elements offer the option of storing different, alternative texts in a form which are then printed depending on the posting procedure.

Example

In the standard form for payment notices, a text element is stored for the case that a credit memo was to be posted and another text element for the case that a partial payment was to be posted for an incoming payment.

For your information, the individual text elements are commented on in the standard forms.

Note

In the letter, you can display the segment text (posting text) of an item. An asterisk (*) must be at the beginning of the text field.
To define your own forms, copy the standard ones and change them. Delete the print texts you do not need. Make sure the numbers of the available text elements and the commentary lines remain for each text element. The commentary lines contain the character /* in the form column.

Activities

  1. Find out the names of the standard forms.
  2. Check whether you can use these forms.
  3. Define and activate your own forms and translate them, if necessary.
  4. Store the names of the forms.

Business Attributes
ASAP Roadmap ID 259   Establish Forms and Messages 
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 SIMG_CFMENUORFBOB96 0 HLA0006520 O HLA0001271 O HLA0001281  
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
V_001F_B V - View SM30 9999999999 Define Form Name 
History
Last changed by/on SAP  19981222 
SAP Release Created in