How to create a validation for a certain document number range?

Good Day!
May I just seek assistance on how to limit a certain document number range from normal posting via F-65?
The scenario is I would like to restrict, say for example Document Number range 07 from transaction FBV1. How do I create a validation for that? I was thinking what to put up in the Check field in the validation.
This is how I set up the pre-requsite for the validation rules:
Pre-requisite: Transaction Code = FBV1
Thanks!

Ok great.. Thanks a lot for the help.If I may just ask one more? =)
What if the scenario is say creating a validation for a certain GL account group?
Scenario: User would like to restrict the transaction FBV1 from posting to a GL account group (e.g. G007) ?
I checked the list of tables and fields in validations, but it seems that the GL account group is not part of the list.
Any help would be greatly appreciated.

Similar Messages

How to create a validation for the project coding mask

Hi,
Would just like to ask how to create a validation for the project coding mask wherein the WBS elements hierarchy will be checked against the template saved. For example,
project coding mask is XXXX-XXXXX-XX-X-X-X-00-X
mother WBS should be XXXX-XXXXX-X and lower level WBS would be XXXX-XXXXX-XX.
The validation should not allow a mother WBS to be XXXX-XXXXX-XX.
How can we go about this?

Hi Jacquiline Bersamin,
You can use validation with the combination of the level and the coding mask.
In the validation:
Pre requisite: WBS level = 1
Validation: Prps-posid = prps-posid :1-12:
Message : Error
If required you can give the parameters for your detail error message.
Please let me know if this does not work.
Thanks
Regards
Srinivasan Desingh

How to create a validation for version in planning

Hello all,
i would like to create a validation for the field 'version'. I have defined 8 different versions, one of them just for planning in orders.
How can i create a sustitution in order to validate that always that they are going to plan in orders, only they are going to allocate the plan in the proper version?
Is there another different way to do this?
Thanks in advance.

Hi,
For planning transactions (except for planned settlement), the validation OKC7 (or substitution OKC9) won't work.
Regards,
Eli

Important : how to create a validation for table field.

Hi all,
I have created a table in which i have date field of format MM/DD i.e char 5.
i want validation that if user creates a entry in date field then if he enters first two digit more then 12 then validation must be their that please enter first 2 digits from 1-12.
similarly for last two digitsi.e it must be from 1-31
so how can i provide this validation.
if u have any confusion in understanding the query please revert.

Declare 3 variables
DD(2) type char
MM(2) type char
Temp(2) type char
Date(5) type char
Get the DD and MM value from your date field
if MM > 12.
    temp = MM.
    MM = DD.
    DD = temp.
endif.
Then concatenate MM & DD into date and save
Hope it helps!
Regards,
Ashok

How to create a spool for the billing document

Hi all
In the ALV report i am getting the
List of billing documents
on the selection of any billinfg document
i wanted to create the spool of the same
is there any way for the same .
please help.

Hi
check with the fun module to get the SPOOL ID of the billing doc
RSPO_RW_SPOOLJOB_PARAMS
Reward points if useful
Regards
Anji

How to create release order for value contract?

dear experters,
I create a value contract by T-code:va41, order type"WK1".I set a Assortment module to this order and mateirl "WKM1" to it.
then I create release order by T-code:va01 with refrence to this value contract,but it set the material "WKM1" to the sales order, and I can't modify this material! I want to put another material which belong to the assortment module in the value contract. I want to know how.
thanks.
Best regards
lance

Assortment Module for Value Contracts
This function enables you to define a list of materials that can be released from a value contract. Materials can be assigned to more than one assortment module.
An assortment module is an entry tool and can be called up from the value contract. It is valid for a certain time period.
If you delete a material from the assortment module, to which a value contract refers, you will be unable to release that material.
In the value contract, only materials with the same sales organization and distribution channel as the value contract can be taken from the assortment module. All the other materials in the assortment module are not displayed in the value contract.
To fulfill both these requirements, two types of value contracts are offered in the standard system:
Value contract type WK 1
You can specify a product hierarchy or a assortment module for value contracts with contract type WK 1. The system will always propose this type of contract, if you want to create a contract for several materials or a certain group of materials. All the materials in the relevant assortment, or belonging to the specified product hierarchy are then relevant for release.
Value contract type WK 2 (material-related)
You can create contracts for one material (usually configurable) with this type of value contract. A software company is an example of where this kind of contract is often used. There, a contract for the value of $500,000 is made with the customer for one specific software product.
You can also agree on the length of the contract for this type. The contract duration can be agreed at item level and can be different from the contract duration specified at header level.
You can store special price agreements for the value contract. These price agreements can then be used at any level. For example, a value contract can contain prices for individual materials, or discounts that are valid for every released material.
Release Orders
The customer fulfills a contract by issuing orders against the contract. The contract does not contain any exact dates for deliveries, so you need to create a sales order to release against a value contract.
When a release order is created for the contract, the system automatically updates the released values in the contract. The release order value is calculated from the total of the open order and delivery values, plus the value that has already been billed to the value contract.
The system also updates the released value for subsequent changes (for example, overdelivery of contract release, price changes in the billing document, partial deliveries, returns, rejection of order items, cancellation or reversal of orders, deliveries or billing documents).
You can create a release order in any currency. The system automatically converts this currency into the one agreed upon in the value contract on the pricing date for the contract release order.
Creating Assortment Modules for Value Contracts
Procedure
To create an assortment module, proceed as follows:
1. From the initial screen choose Logistics >Sales and Distribution >Master data.
2.Choose Products >Value contract - Assortment module > Create.
You will then be in the Create assortment module: Initial Screen.
Module type 6 is defined for the value contract.
3. For external number assignment, enter a module number.
You can then use existing modules as a reference by entering the name of the module under reference.
4. Choose Enter.
5. Enter a short description for the module.
6. Enter a validity period for the product proposal.
During a release, the system checks if the release date lies within the validity period.
7. Create the materials that you wish to assign as items to a module.
You can display a list of materials as a product proposal, which you can then copy into the assortment module. To do this, choose Suggest material, enter the selection criteria in the subsequent screen and copy the selected materials to the items. Use Edit > Delete item to delete the materials that you do not want to copy to the assortment module.
8.Save your entries.
Also Please check the copy control in VTAA
Regards,
Anbu

How to Create a Validation based on a Z table

I want to create a validation for t-code FB50 so that for any line item that contains a GL Account listed in a table, the validation would then check to see if the field Trading Partner is populated.
My question is How do I set up the validation so that the values in the table are referenced? I don't want to have to continually update the valid GL accounts in a set. I want the table to hold the values. The business users have a custom t-code to update the values in the Z table.
The Z table contains the field HKONT (GL Account). The table contains 1 record (it could contain more) with GL Account 123456.
My attempt was to create a set (Z_TP_ACCTS) that was based on the Z table and the corresponding field. I then set up my validation to compare the value entered in FB50 (BSEG-HKONT) to look at the set. My understanding is that the value would be compared to the values in the table, but my tests are failing. I did not enter any values in the set.
Any advice / help would be appreciated.

Hi
You will have to use an user exit to call up the Z Table to check for your requirement. There are lot of postings on SDN to use an user exit in FI Validations. The standard module pool provided by SAP is RGGBR000 for FI Validations. You can write a form in this.
Additionally you also have the option of using a BTE for this. The one I can recollect are 00001011 or 00001085
Thanks & Regards
Sanil Bhandari

Creating a Validation for WBS Element in the Asset Master Record

I would like to know how to create a validation in the AMR for the WBS Element field. I would like to have a particular Business Area when used be required to only use a WBS element that starts with, let's say, AL. Can someone shed some light on how I would set up my check in OACV?

Hello
You can validate or substitute data directly at the input stage. You make the settings for validation and substitution in the Implementation Guide (IMG) for Controlling, under Controlling General ® Account Assignment Logic ® Define Validation or Define Substitution
Substitution and validation are only intended for actual postings
For a complete description of validation and substitution, see the SAP Library under Accounting - FI Financial Accounting ® Special ledger ® Tools ® Validation and Substitution Rules
Coordinate with ABAPer and make settings.
Reg
*assign points if useful

How to change bucket capacity for a certain date range (duration)?

Hi,
I need to update the bucket capacities of Resource at Vendor location in APO live cache for a particular period using BAPI_RSSRVAPS_CHANGEMULTI.
Here I am executing BAPI by passing -
Import Parameters:
LOGICAL_SYSTEM
COMMIT_CONTROL
PLANNING_VERSION
Tables:
RESOURCE_HEAD
(RESOURCE = Resource " Test123
LOCATION = Vendor Number/Loctaion
CAPACITY_A = 5000.000
NUM_OF_PERIODS = 001
PERIOD = 02 " Day Wise
UTIL_BUCKET = 100.000 )
RESOURCE_HEAD_X
(All corresponding fields X)
RESOURCE_QUANMODEL
(RESOURCE = Resource " Test123
VERSION = 01
ENDDA = 02/25/2011
BEGDA = 02/21/2011
QUANMODEL = 8000 )
RESOURCE_QUANMODEL_X
(All corresponding fields X)
[ I have a capacity variance:
Resource = Test123; Capacity Varient = 01; Valid From = 02/21/2011
Valid To = 02/25/2011; Bucket Util Rate = 100.000; Qty/Rate definition = 8000 ]
Now, while I execute /SAPAPO/RES01 to display Capacity for that resource-Location-PlanningVersion, Its showing that 'Bucket Capacity' and 'SNP Bucket Capacity' get changed into 5000. But this change happend for all the days and not only for the duration I passed into Bapi (From BEGDA to ENDDA).
How to change bucket capacity for a certain date range (duration)? Any help please.
Thanks
Roy

I did it myself. Hence closing the thread.
Solution:
1. Get RESUID from /SAPAPO/RESKEY table by passing Resource as NAME.
2. Call Function Module /SAPAPO/CRES_QUANPROF_UPDATE
3. Call Function Module /SAPAPO/CRES_SAVE_FROM_BT
For further help, change manually a single record in the 'capacity profile' in TXN /SAPAPO/RES01 and debug both the FM mentioned above.
BR
Roy

How to create authorisation object for save button please help in abap

how to create authorisation object for save button please help in abap

Hi
In general different users will be given different authorizations based on their role in the orgn.
We create ROLES and assign the Authorization and TCODES for that role, so only that user can have access to those T Codes.
USe SUIM and SU21 T codes for this.
Much of the data in an R/3 system has to be protected so that unauthorized users cannot access it. Therefore the appropriate authorization is required before a user can carry out certain actions in the system. When you log on to the R/3 system, the system checks in the user master record to see which transactions you are authorized to use. An authorization check is implemented for every sensitive transaction.
If you wish to protect a transaction that you have programmed yourself, then you must implement an authorization check.
This means you have to allocate an authorization object in the definition of the transaction.
For example:
program an AUTHORITY-CHECK.
AUTHORITY-CHECK OBJECT <authorization object>
ID <authority field 1> FIELD <field value 1>.
ID <authority field 2> FIELD <field value 2>.
ID <authority-field n> FIELD <field value n>.
The OBJECT parameter specifies the authorization object.
The ID parameter specifies an authorization field (in the authorization object).
The FIELD parameter specifies a value for the authorization field.
The authorization object and its fields have to be suitable for the transaction. In most cases you will be able to use the existing authorization objects to protect your data. But new developments may require that you define new authorization objects and fields.
http://help.sap.com/saphelp_nw04s/helpdata/en/52/67167f439b11d1896f0000e8322d00/content.htm
To ensure that a user has the appropriate authorizations when he or she performs an action, users are subject to authorization checks.
Authorization : An authorization enables you to perform a particular activity in the SAP System, based on a set of authorization object field values.
You program the authorization check using the ABAP statement AUTHORITY-CHECK.
AUTHORITY-CHECK OBJECT 'S_TRVL_BKS'
ID 'ACTVT' FIELD '02'
ID 'CUSTTYPE' FIELD 'B'.
IF SY-SUBRC <> 0.
MESSAGE E...
ENDIF.
'S_TRVL_BKS' is a auth. object
ID 'ACTVT' FIELD '02' in place 2 you can put 1,2, 3 for change create or display.
The AUTHORITY-CHECK checks whether a user has the appropriate authorization to execute a particular activity.
This Authorization concept is somewhat linked with BASIS people.
As a developer you may not have access to access to SU21 Transaction where you have to define, authorizations, Objects and for nthat object you assign fields and values. Another Tcode is PFCG where you can assign these authrization objects and TCodes for a profile and that profile in turn attached to a particular user.
Take the help of the basis Guy and create and use.
Regards
ANJI

How to create an extension for generated type idoc

Hi all,
Can u please look into this
How to create an extension for generated type idoc ? for example Idoc type BATMAS02

Enter transaction WE30 (ALE->Extension-> IDOC types->Maintain Idoc type)
- Type in your name of the extended IDOC type (usually starting with 'Z') and click on the Basic IDoc type, click the create icon.
- Click on Create new and enter a description and press enter.
- Click on ZIDOCTYPE01 and then on the Create icon.
- Enter ZIDOCTYPE as the segment type, click on Segment Editor.
- Enter a description for your segment type and create.
- Enter a description for your segment, enter each field required in your IDoc and press enter to validate.
- Save and generate, press back
- To release the segment choose Goto, Release from the menu.
- Check the box on the line of your segment.
- Save, back and enter.
- Your Idoc type structure should be displayed with your new segment.
- Save and back.
- To release the Idoc type choose Extras, Release type from the menu and Yes.
ALE FUNCTION MODULE ENHANCEMENTS
Having extended the IDOC type to contain additional fields for an inbound or outbound application, you now want to enhance ALE function modules for populating the additional segment on the outbound or applying the additional segment data on the inbound application.
The core working code for ALE processes for a given application area is always encapsulated in ABAP/4 function modules. These function modules are associated with such control information as message types and process codes. So the ALE process checks this control information and derives the name of the function module to invoke for that particular IDOC processing from certain database tables. These function modules contain objects known as customer functions, which can be considered SAP Enhanced user exits. A function module is called at a particular point during the processing of the main program or function module, and it can be used to influence data processing at that point by adding code to the customer function. The customer function behaves like a normal function module and has import and export parameters, tables (internal tables) statement, and exception processing. Unlike a conventional user exit, customer functions give you the ability to modify only data available to you by the function moduleâs parameters and internal tables. While most ALE/EDI function modules are supported by customer functions, there are ALE/EDI processes that still use conventional user exits. There are a few ways to determine which function module to enhance for a given message type/process code:
For master data distribution, from SALE go to Extensions -> Master data distribution -> Setup additional data for message types. Search for message type DEBMAS in this example. You see an entry for DEBMAS associated with function module MASTERIDOC_CREATE_SMD_DEBMAS. This data is stored on table TBDME. The function module names for all master data message types follow this pattern: MASTERIDOC_CREATE_SMD_messagetype. This function module calls another function module of name MASTERIDOC_CREATE_DEBMAS or MASTERIDOC_CREATE_messagetype. Search for the words customer function, and you find several hits that can be used to add code to the function module.
From WEDI got to Control -> Inbound process codes -> Inbound with ALE service -> Processing by function module (transaction WE42), or from WEDI go to Control -> Outbound process codes -> Outbound with ALE service -> With function module (transaction WE41). There will be function modules associated with the process codes. For inbound, the function modules usually follow this pattern: IDOC_INPUT_messagetype: for example, IDOC_INPUT_CHRMAS for inbound characteristics master.
Use transaction WE57 or from WEDI go to Development -> Message/Application Object. The entries list the function module, Business Object, message type, and IDOC type that are used for inbound ALE/EDI interfaces.
Customer functions are not specific only to ALE and EDI but also to all programs/modules in SAP R/3. Customer function is a SAP enhancement component; the other two types are menu and screen enhancements.
All customer function exits are maintained in SAP enhancements and are found by using transaction SMOD. After executing transaction SMOD, pull down (F4) on the enhancement name field, and execute again. This provides you with a list of all SAP enhancements available. SAP enhancements are grouped by development class pertaining to an application area. Choose Application development R/3 SD master data distribution for development class VSV to lead to a screen that lists VSV00001 as an enhancement (see Figure 5). Press Component +/- to display its function exit components. There are four possible components listed, all of which are function exits (and are function modules) that are called from the ALE function modules in the form Call Customer Function Î001â. This is a special occurrence of the ABAP statement Call. Go to item Exit_SAPLVV01_ 001, which you need to enhance for the Customer Master outbound example of an IDOC extension. In the ALE-function module MASTERIDOC_CREATE_DEBMAS, the statement CALL Customer Function 001 is translated in the background to call component EXIT_SAPLVV01_001. Although this function exit can be edited using transaction SE37, you will use a simpler approach.
When you use SAP enhancements and their components, you manage them with an SAP object known as a project, which is like an envelope containing the selected enhancements and their components. A project can be used to control the execution of components and to transport them to other clients and instances in SAP. Basically, the process involves creating a project, including enhancements and components that are to be enhanced, editing the components, and then activating the project. The following process creates a project for our example Customer Master IDOC extension:
Execute transaction CMOD.
Enter name of project, say CSTMAST1.
Click on Create.
Enter a description of the project.
Save.
Click on SAP Enhancements.
Enter VSV00001 for Enhancement.
Save.
Once youâve created the project, edit the function exit components and activate the project. Remember that the code in the function exit enhancement will execute only if the project is activated. In fact, this is a convenient SAP enhancements feature, whereby the work in progress (developing code in the customer function) will not affect users of that application. When the code is completed, the project can be activated so the enhanced functionality takes effect. It can also be deactivated for maintenance.
As mentioned earlier, customer functions (function exits) are embedded in ALE function modules and can be used to influence the creation and modification of IDOC data on an outbound application or to post additional or modified IDOC data to an inbound R/3 application. Function exits are similar to regular function modules, with import/export parameters, tables (internal tables), and exceptions.
The two important factors to consider while developing the customer function are:
1. The point in the ALE function module where the function exit occurs
2. The data made available by the customer function that can be modified or posted to the R/3 application, based on the direction.
Because some function modules have several customer functions, it is critical to choose the function exit best suited for that particular enhancement. Do not attempt to perform activities that the function exit is not designed for. The importance of this point is illustrated by the following description of enhancing function modules for outbound and inbound ALE interfaces.
Outbound interfaces. In an outbound ALE interface you use function exits (customer functions) to populate additional segments created by an IDOC extension or to modify the existing IDOC data segments as per business requirements. Previously, you identified that enhancement VSV00001 has a component EXIT_SAPLVV01_001 (function exit), which can be used for populating the additional data segment Z1SADRX that you created in the IDOC extension ZDEBMASX (IDOC type ZDEBMASZ, based on Basic IDOC type DEBMAS02). You also learned that the ALE function module that calls this function exit is MASTERIDOC_CREATE_DEBMAS, which has a statement Call Customer Function 001.
Browse the function module MASTERIDOC_CREATE_DEBMAS using transaction SE37. You will find that this customer function is invoked for every segment of IDOC type DEBMAS02. In fact, the function exit is called soon after the creation of an existing segment has been populated with data and appended to the IDOC data table (internal table). Also, the function exit is exporting the message type, IDOC type, and the segment name and is importing the IDOC extension type. It is also passing the IDOC data internal table. This indicates that the ALE function module is allowing you to populate additional segments for every existing segment and modify the existing segmentâs data.
Letâs write ABAP/4 code to accomplish the task of populating IDOC segment Z1SADRX with a contact personâs business address:
From SE37, display function module MASTERIDOC_CREATE_ DEBMAS.
Find Customer Function 001.
Double-click on 001.
The function EXIT_SAPLVV01_001 will be displayed.
Double-click on INCLUDE ZXVSVU01.
You will be asked to create a new include object. Proceed as desired.
Enter code (as in Listing 1).
Be sure to perform a main program check (Function Module -> Check -> main program) and extended program check (Function module -> Check -> Extended check).
Now that you have extended the IDOC and enhanced the ALE function module based on the requirements for the contact personâs business address on the Customer Master, letâs test the interface. You should create a logical system and define a port for this interface. You should also configure the Customer Distribution Model to indicate that message type DEBMAS is being distributed to this logical system. The only difference in configuration between a regular outbound ALE interface and an enhanced one is the partner profile definition. While maintaining the outbound parameters of the partner profile, make sure the IDOC type is ZDEBMASZ. The fields for Basic IDOC type and extension type are automatically populated with DEBMAS02 and ZDEBMASX, respectively.
To maintain the contact personâs business address of a customer:
Use transaction BD12 or from BALE go to Master Data ->Customer -> Send and send that Customer Master record by executing the transaction after filling in the relevant fields such as customer number, message type, and logical system.
Use transaction WE02 or WE05 to verify the IDOC created. You should see the new segment Z1SADRX populated with the correct data.
With SAP releases below 4.5B, you cannot capture changes to business address through change pointers because a change document object is not available for capturing business address changes, and also earlier releases have not been configured to write change documents for a contact personâs business address. If you would like this functionality, you can either create change document objects, generate function modules to create change documents, and perform ALE configuration to tie it in, or make a cosmetic change to the contact person screen data while changing the contact personâs business address so that it gets captured as a change to the Customer Master. Subsequently, the ALE enhancement that you performed captures the contact personâs business address.
Inbound interfaces. The process for enhancing inbound ALE interfaces is similar for outbound, with a few exceptions; specifically in the coding of customer functions (function exits) for the ALE/EDI function modules.
The first step is to create an IDOC extension for the specific Basic IDOC type by adding new segments at the appropriate hierarchy level: that is, associated to the relevant existing segment. Populate the data fields on the new segments with application data by the translator or external system/program before importing them into the R/3 System. Then, find the ALE function module that is invoked by the inbound processing. By browsing through the code or reading the documentation on the function exit enhancements using the SMOD transaction, identify the function exit in which you should place your code. The technique used in the code to post the additional or modified IDOC data to the application can vary based on the application rules and requirements, the data available at that point in processing, and the application function modules available to update the application tables. It is important to search first for application modules that process the data and see if they can be called within the function exit. If the additional data in the extended segments in specific to a custom table or resides in nonkey fields of a single or small set of tables, you may be able to update it directly by SQL statements in the function exit. This approach should be carefully evaluated and is certainly not highly recommended.
Another option is to use Call Transaction from within the function exit to process the additional data. For example, in the case of message type WMMBXY for inbound goods movements from a warehouse management system, the standard interface creates batches for materials, but does not update its characteristics. In such a case, you can use Call Transaction MSC1 to create the batch and assign characteristic values to it from within the function exit provided.
regards,
srinivas

How to create a macro for a planning type in MC8b transaction

Hi,
I am presently working for a product allocation demand, which have a information structiure with characteristic and key field.
the characteristic are production allocation quantity, incoming order quantity, and open order quantity.
i have created a planning type in which the data updation takes from the excel file to the planning type in mc95.
but i need to create a macro for this planning type .
can any body give the details information how to create a Macro for a planning type.
Thanks and regards
GopalKrishna

Dear Gopal
May be the link would be helpful to you.
[Planning Types and Macros|http://help.sap.com/saphelp_46c/helpdata/en/a5/631cc443a211d189410000e829fbbd/frameset.htm]
Drill down the left tab once you opened the link, for more information.
Thanks
G. Lakshmipathi

How to create custom infotype for training and event management

hai freinds can any one tell me how to create custom infotype for training and event managment with following fields
PS No PA0000-> PERNR
Name - PA0001 -> ENAME
IS PS.No. PA0001-> PS no. of Immediate Superior
IS name PA0001 -> ENAME
thanx in advance
afzal

Hi,
Your question is not clear for me. Since it is a TEM infotype, it could be a PD infotype.
If you wish to create a PD infotype, use transaction PPCI to create the infotype.
But before that you need to create a structure HRInnnn (where nnnn is the infotype number) with all the fields relevant for the infotype.
If you wish to create a PA infotype, use transaction PM01 to create the infotype.
But before that you may be required to create a strcuture PSnnnn (where nnnn is the infotype number) with all the fields relevant for the infotype.
Regards,
Srini

How to create one TO for multiple TRs

Dear All,
how to create one TO for multiple TRs, kindly suggest me
Regards,
balu

As for your question: it is discussed in sAP online help:
http://help.sap.com/saphelp_erp60_sp/helpdata/en/c6/f841f24afa11d182b90000e829fbfe/frameset.htm
Sorry I misunderstood your question.
The above mentioned solution won't create one single TO from multiple TR.
Edited by: Csaba Szommer on Aug 11, 2010 9:46 AM

How to create one checksum for 264 vis

Hi,
How to create "one Checksum" for 264 Vis.These 264 Vis are Interlinked if i change code for any .vi the checksum Should be update.This checksum is shown on the main window.
Regards
Ravindranath
Solved!
Go to Solution.

Here's a slightly simplified version (saved in 8.6). There's no need for the Get/Set File Position. The file position is already being incremented with the read.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
Attachments:
Multiple File MD5 Checksum (Version 8.6).vi ‏23 KB

How to create a validation for a certain document number range?

Similar Messages

Maybe you are looking for