Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM-BTX-BF-IF (Application Component) R/3 Interface for Business Transactions⤷
VA (Package) Application development R/3 Sales
Basic Data
| Data Element | GRPNO |
| Short Description | Number of the routine used for copying |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | GRPNO | |
| Data Type | NUMC | Character string with only digits |
| Length | 3 | |
| Decimal Places | 0 | |
| Output Length | 3 | |
| Value Table | TFRM |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ROUTINE | |
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Routine |
| Medium | 15 | Form routine |
| Long | 20 | Form routine |
| Heading | 3 | RNo |
Documentation
Definition
Number of a subroutine (= form routine), that checks a requirement at a specific time.
Use
The standard SAP system contains some standard routines for checking requirements when copying. You can also define your own routines according to the needs of your company.
Example
If you copy a quotation to a sales order, the system can check every quotation item to ensure that the customer had not rejected them for any reason.
Procedure
The system proposes a routine for checking copying requirements according to the type of document to be copied. If you do not want to use the proposed routine you can do one of the following:
- Enter the number of another routine.
- Change the routine yourself and define specific requirements that should be checked. (Before you change a routine, you should check if it is used somewhere else, in order to avoid unwanted changes at another point).
- You can enter the number of a new routine and define it using SAP development tools.
Note
You can find the available routines in Customizing for copy controls for each document (e.g. maintain copy control for sales documents).
Supplementary Documentation - GRPNO 0001
Use
The confirmed quantities are only transmitted if the requirement is met.
Procedure
Examples
Dependencies
Supplementary Documentation - GRPNO 0002
Use
Here you can specify the number of a routine in risk management that contains the conditions for when there should be no payment guarantee for the specified form of payment guarantee.
You can define your own routines to meet your company's requirements.
Procedure
Examples
The routine could contain the following conditions:
- Item values under $10 are not guaranteed
- No payment guarantee for certain product hierarchies or product group.
Dependencies
Supplementary Documentation - GRPNO 0003
Use
Here you can specify a routine number that contains conditions for when a credit limit check should take place.
Examples
The routine could contain the following conditions:
- No check, if the document does not contain any items
- No check, if the new net value does not exceed the old net value
Caution
Take into account the importing and exporting parameters in the example routines delivered with the standard system. Ensure that the coding in the routine is consistent with the coding for risk management.
History
| Last changed by/on | SAP | 19991108 |
| SAP Release Created in |
