Hierarchy
EA-FIN (Software Component) EA-FIN⤷
CA-JVA (Application Component) Joint Venture und Production Sharing Accounting⤷
GJV2 (Package) Joint Venture Development
IMG Activity
| ID | SIMG_ENV_0007B | Validation |
| Transaction Code | S_KK4_66000107 | IMG-Aktivität: SIMG_ENV_0007B |
| Created on | 19991013 | |
| Customizing Attributes | SIMG_ENV_0007B | Validation |
| Customizing Activity | SIMG_ENV_0007B | Validation |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_ENV_0007B |
You can define validations that will be applied during data entry to postings with JVA-related data. These validations can be used to control data that is entered in the JVA single item ledger JVSO1 via the special ledger table JVAP.
Validations can be applied to any of the fields stored in the special ledger table JVAP that are significant to JVA. JVAP populates the JVA single item ledger JVSO1.
Example
Validation can be applied to exclude postings to selected cost objects.
Requirements
Standard settings
Recommendation
Activities
Defining a validation in JVA is a three-step process:
- Identify the JVA company and call-up point (only 2 - document item is allowed)
- Define the validation name, description, and specific logic
- Assign the validation to the company and call-up point combination
1. Identify Company and Call-up Point
On the Change Validations for JVA Documents: Overview screen, select New Entries and enter the code for the JVA company in the CC field and the call-up point 2 in the CallPnt field.
Select Environment > Validation.
2. Define Name, Description, and Logic
On the Change Validation: Initial screen, enter the name for the new validation in the Validation field and select Validation > Create.
On the Create Validation: screen, enter the long text for the new validation and select Insert entry to define the logic.
On the Create Validation screen for validation step one, enter the description for the text and any prerequisites and checks for the validation in boolean terms.
3. Assign Validation to Company
Return to the first validations screen and assign the new validation to the company and call-up point combination
To activate the validation for the company, you must assign an active code of 1 to the validation.
Further notes
There is a separate JVA authority for validations and susbstitutions.
Business Attributes
| ASAP Roadmap ID | 257 | Create User Exits |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 1 | 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_ENV_0007B | 0 | ALR0002181 | Joint Venture und Production Sharing Accounting |
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_T8JZVAL | V - View | GJBV | ENV_0007B | Assign Validation to JV company |
History
| Last changed by/on | SAP | 20010305 |
| SAP Release Created in |
