validation sap

-


=Uzzzz (zzzz = up to 4 characters - this is true for Document Level validations - call point 3 - *Header Level & Line Item Level - call points 1 & 2 - allow up to 30 charaters.) /NORFB->Bus.transactions->Base parameters->Validation /NORFB->Bus.transactions->Base parameters->Substitution
Example
=ULTE "FI_DOCU 001 "Parked SA,FY,SI=>long text CORRESP. " =U&VALID_WBS_IN_ZUONR "FI_ITEM 011 Spon.Res: Check WBS valid in ZUONR" * changed in 4.5B (* Form UFIA -- formerly U&VALID_WBS_IN_ZUONR)
User exits are form routines that the user programs. There are two types of user-exits:
1. Validation exits are used in the prerequisites and checks. They have either the value 'T' for true or 'F' for false. They are interpreted as a part of the logical statement, like a constant or field comparison. For this type of user exit, you must fill a parameter with the results of your check ('T' for true; 'F' for false).
Example
FORM Uzzzz USING B_RESULT. "'T' or 'F' from program ZGGBR000 (ZGGBRI03)
2. Substitution exits are used to change one or more fields. However, you can only change those fields that are permitted in the Boolean class for the substitution. You can display these fields by selecting the following menu options in substitution maintenance: <Extras -> Fields for substitutions>
Example
FORM Uzzzz USING COST_CENTER. from program ZGGBS000 (ZGGBSI02) Substitution Fields can be found from this window   /NORFB->Bus.transactions->Base parameters->Substitution->Call Pnt 2->Substitution step 3->Extras->Substitution flds
The name of the form pool (e.g., ZGGBR000 & ZGGBS000) that contains your user exit must be stored in table T80D.
Note
1. Data declaration
Tables and field stings cannot be declared in form routines, so that the contents can be used along with the calling transaction.
2. Parameter definition
It is important that you make declare the code generation program for your user exit; how many and what type of parameters you are using for the user exit. You do this by entering your newly defined user exits in the form routine GET_EXIT_TITLES. found in program ZGGBR000 (ZGGBRTIT) found in program ZGGBS000 (ZGGBSTIT) One exception is the parameter for the results of a validation exit. You must not declare this, it is automatically generated be the system. What types of parameters are available and how you use them is described in the online documentation. When creating your user exits, you can use the example form pools delivered by SAP (RGGBR000 for validations; RGBBS000 for substitutions) as a reference. We recommend that you copy the example form pools delivered by SAP when creating your own user exits. In these example form pools, entries already exist in the form routine GET_EXIT_TITLES for the examples delivered. The GET_EXIT_TITLES must absolutely exist in your form pool. 
You can find additional information on the creation of user exits in the online documentation on validations and substitutions.

SAP exits

SAP exits are form rountines programmed by SAP. The name of the form pool is SAPFGBEB.
Syntax:
=Szzzz (zzzz = up to four characters) FORM Szzzz using B_result. "'T' or 'F'
Example
=S01 "SAP exit S01"
Display description of T80D configuration
Return ->
Change Valid

Comments

Post a Comment

Popular posts from this blog

Bank Accounting (FI-BL)

-
  Bank Accounting (FI-BL) Bank Accounting (FI-BL) is a component of the SAP Financial Accounting (FI) module that focuses on managing bank transactions and bank statement processing within an organization. It facilitates the efficient handling of financial transactions with banks and ensures accurate reconciliation of bank accounts. Key features and functionalities of the Bank Accounting (FI-BL) module include: 1. Bank Master Data Management: FI-BL allows the creation and maintenance of bank master data, which includes information about bank accounts, bank branches, and relevant details for each bank. This data is used for accurate processing and recording of bank transactions. 2. Bank Statement Processing: The module supports the automatic processing of electronic bank statements received from banks. It includes functionalities for importing bank statements, automatically matching transactions with open items in the system, and generating accounting entries based on the statement ...
Read more

Funds Management (FI-FM)

-
  Funds Management (FI-FM) Funds Management (FI-FM), also known as Budgetary Control or Budget Management, is a component of the SAP Financial Accounting (FI) module that focuses on managing and controlling budgets within an organization. It helps organizations effectively plan, allocate, monitor, and control their financial resources. Key features and functionalities of the Funds Management (FI-FM) module include: 1. Budget Planning: FI-FM supports the creation and maintenance of budgets for different organizational units, cost centers, projects, or funds. It allows organizations to define budget structures, set budgetary limits, and allocate funds based on business requirements and strategic objectives. 2. Budget Monitoring and Control: The module provides functionalities for monitoring and controlling budget utilization. It includes tools for tracking actual expenses and revenues against budgeted amounts, generating budget consumption reports, and issuing budget warnings or aler...
Read more

R/3 Architecture:

-
R/3 Architecture:             SAP uses the industry specific 3-Layer Architecture and named it as R/3 Architecture.             It consists of three 3 Layers 1. Presentation Server/ Layer/ Tier 2. Application Server 3. Database Layer 1. Presentation Server:                         It is a client for all the SAP Solutions. It is also referred as SAPGUI. There are three 3 types of SAP GUI                         1. SAP GUI for windows     (On Windows OS)                         2. SAP GUI for J...
Read more