New features added, version 7.5.3 Patches, 8.1 Patches
Program GPTM, Posting Template Maintenance, is used to enter and maintain the posting parameters for each posting interface. It is recommended that only implementers and programmers be allowed access to this program. However, simple SQL statements may be able to be entered by a normal user after consultation with a programmer or implementer.
* At least one default posting parameter record must be created for each posting type.
* There are two ways to create a posting parameter record, in program GPTM, Posting Template Maintenance, or in program GPTE, Posting Template Value Entry.
Creating a posting parameter record in program GPTE, Posting Template Value Entry, requires an abstract template to be created in program GPTM, Posting Template Maintenance.
* For example, you might want to create an abstract template if you were posting revenue by product group and you had an excessive number of product groups.
* By creating an abstract template, you could create a base form in program GPTM, Posting Template Maintenance, and have a data entry clerk enter the information in program GPTE, Posting Template Value Entry.
* Since only a few fields can be altered in program GPTE, Posting Template Value Entry, this protects against major mistakes.
The information entered in this program for an abstract template can not be changed in program GPTE, Posting Template Value Entry.
* There are only three fields that can be altered in program GPTE, Posting Template Value Entry, the account numbers, the Argument Operator, and the Argument Item.
* These fields can only be changed only if certain conditions are met when the abstract template is set up in this program.
* The account number fields must be left blank, the Argument Operator must be set to ?, and the Argument Item field must have a ? in it.
Posting convention in NDS Applications: a positive entry is always a debit entry and a negative entry is always a credit entry to an account.
Sales Interface Default Posting Parameter Requirements
Account Segments and Posting Parameter Records
NULL and Not NULL Argument Values
Creating a posting parameter record in program GPTM, Posting Template Maintenance
Creating an abstract template for use in program GPTE, Posting Template Value Entry
Accounting for Commitments Posting Types
Accounts Payable Posting Types
Bank Reconciliation Posting Types
Manufacturing Interface Posting Types
Miscellaneous Applications Posting Types
Project Tracking Interface and Posting Parameters
Project Tracking Posting Types
RMA / Service Interface Posting Types
Posting Setup for Standard Cost Manufacturing
Tricks for Posting Template Setup
Default posting parameters are used by the system when a transaction is being posted and it does not meet any of the requirements on other parameter records. With default posting parameter records, the system still has a general ledger account to which it can post the transaction, and the posting will not be ‘lost'. It is strongly recommended that you set up a default posting parameter record for each post type in each posting interface.
Default posting parameters are those for which the Default flag is set to on. The flag is set to on automatically when the Argument Item or Value field is set to ANY.
You must set up default posting parameter records for the following posting types in the sales interface:
CASH
A/R
CDSC
DPST
WTDN
WTUP
Default posting parameter records are those that are set up by location with the Argument Item or value set to ANY. Program ARPE, Cash Receipts Entry, uses the default posting parameter records. If these records are not entered here, you will receive errors when you run program ARPE, Cash Receipts Entry.
Account segments can be used in the parameter records to record a posting parameter value as a column reference in the account number.
* For example, if you had multiple plants, and you wanted the plant code in which the transaction was entered to be recorded in the account number, you could set up an automatic undefined account segment to record the plant code. This allows one plant parameter record for multiple parameter values.
The following rules apply:
* Defined, Soft-Defined, and Undefined segments must have accounts created in program GLTM, Account Maintenance, containing the segment values for the parameter items or the accounts will not post.
* Automatic Undefined segments will have account numbers created with the parameter item in the segment when they are posted.
* Account numbers with automatic undefined segments must have an existing default account number created in program GLTM, Account Maintenance. For example, if the automatic undefined segment of an account number consists of the last three characters in the account number, the account number 200-10000-00-342 must have the default account of 200-10000-00-000. When accounts are created with automatic undefined segments, the default values for the new account are taken from the default account in program GLTM, Account Maintenance.
* Only parameter items entered in program GPMM, Posting Parameter Item Maintenance, can be recorded in an account segment as a column reference.
* When entering the parameter item as a column reference, it must be preceded and followed by both the segment separator and a caret (^). For example, if you were entered the plant code in an account, and the segment separator was a dash (-), the account number would look similar to this. 200-41100-00-0-^PLANT_CODE^-000.
* If the column reference is contains more characters than the segment length allows, the column reference will be truncated to fit the segment. Characters will be removed according to the fill direction for the segment in program GMDS, Define GL Structure.
* If the column reference contains less characters than the segment length allows, than characters will be added to fit the segment. Characters will be added according to the fill direction for the segment in program GMDS, Define GL Structure.
* Date column references are converted to YYMMDD character format before use in the account number. Currently, you cannot extract a month only number into a segment.
If you are setting up a posting parameter for occasions when a particular parameter item is NULL or Not NULL, it should be noted that this condition always needs to be spelled out in a restriction statement with its own statement as in the following example. It is essential that the precedence be set to 1 so the statement will be written using parenthesis as follows:
1. The program opens in query mode. In the Posting Interface field, enter the posting interface for which you are entering posting parameters in the upper block of the program and press [Execute Query].
* Use the Sort By field to sort the templates displayed in the middle block. Choices are Template No and Score.
* To view existing posting parameter records, execute a query in the middle block of the program.
2. In the middle block, to add a new record, press the [New Record] button.
3. In the Template ID field, enter a unique template identifier.
* If you wish to copy the posting parameters from an existing template, enter the template identifier in the Copy From field, and press the [Copy] button.
* If you leave this field blank, a unique template ID will be generated when you commit.
5. Set the Template Type pop-list to Value Set. This indicates to the program that this is a posting parameter record.
* Setting this pop-list to Abstract indicates that the posting parameter record will be competed in program GPTE, Posting Template Value Entry.
6. The pop-list to the right of the Template Type pop-list indicates whether this posting type will generate postings or be posted to the general ledger.
* Select Post This if you wish postings of this type to be posted to the general ledger. You will need to enter general ledger accounts to which the values will be posted.
* Select Suppress to prevent a posting type from creating general ledger postings. No general ledger accounts are required when Suppress is next to the Posting Type.
* Note: Whenever a suppressed posting is discovered by the program, it does not proceed to the next possible match. If you have sets of postings, as in the case of SLAC and SLXP, if one exists as a suppressed and the other side is not there or not suppressed then you get an out of balance invoice.
7. In the Post Type pop-list, select the posting type for which you are entering a posting parameter record. At least one record must be created for each posting type.
8. The Entry Type pop-list in the header determines whether you must enter either a debit or credit account or both debit and credit accounts.
* If the pop-list is displaying 1-sided, only one account must be entered, either debit or credit.
* If the pop-list is displaying 2-sided, both a debit and a credit account must be entered.
* The Entry Type for a posting interface is defined in program GPIM, Posting Interface Maintenance.
9. In the Debit Account field, enter the debit account to which journals created for this posting type will be posted.
10. In the Credit Account field, enter the credit account to which journals created for this posting type will be posted.
* When entering manufacturing posting templates in program GPTM, Posting Template Maintenance, if the credit and debit accounts are the same, postings will not be created for transactions meeting that template's criteria.
* You can enter the parameter item in place of the account segment. For more information, see Account Segments and Posting Parameter Items*Account_Segments_Posting.
* You can do this for all account segment types. However, if the account segment type is Defined, Soft-Defined, or Undefined accounts must be created in program GLTM, Account Maintenance, containing the segment values for the parameter items or the accounts will not post.
* Automatic Undefined segments will have account numbers created with the parameter item in the segment when they are posted.
* For example, if you wanted to record the plant code, and the account number was 200-41000-00-0-00000-000, you would replace it with the following: 200-41000-00-0-^PLANT_CODE^-000
11. In the field to the right of the Post Type pop-list, enter a score value. The system, when searching for an account to which to post, uses the score to determine the order of the search.
* It will search through the posting parameter records in descending order by the value in the score field.
* A score with the value of 90 will be evaluated for matching parameters before a score with the value of 10.
* When the system finds an exact match between the parameters and the transaction that it is trying to post, it takes that account numbers from that posting parameter record and looks no further.
* Note: Whenever a suppressed posting is discovered by the program, it does not proceed to the next possible match. If you have sets of postings, as in the case of SLAC and SLXP, if one exists as a suppressed and the other side is not there or not suppressed then you get an out of balance invoice.
12. Press [Commit].
13. In the lower block, enter the arguments that will be used to determine whether the posting will be made to this account.
14. In the Seq field, you can assign a sequence number to each line. The sequence number determines where the parameter item is located in the SQL statement. Those with a lower sequence number will be placed first.
* If you do not assign a sequence number, it will be assigned when the record is committed.
* Those with a lower sequence number will be placed first.
15. Set the Precedence pop-list is used when generating the SQL statement from the information entered in the lower block. The precedence determines when, where, and how many parentheses will be placed in the SQL statement.
* A zero indicates that no parentheses will be placed. A one indicates that one set of parenthesis will be placed.
* The system will evaluate parameter items with a higher precedence before evaluating those with a lower precedence. If the parameter items are the same, they are evaluated from left to right in the SQL statement.
* For example, if the first parameter item has a precedence of zero, the second parameter item has a precedence of one, the third item has a precedence of one, and the fourth item has a precedence of zero, then a single parentheses will be placed around the first, second, and third items, but not the fourth.
16. In the Link Op pop-list, select the link operator for the posting parameter record.
* The first Link Operator must be a WHERE statement.
* Each Link Operator that follows the first link operator connects the parameter item to the parameter item before it.
* For explanations of the AND and OR Link Operators, see the SQL Language Reference Manual.
17. In the Parameter Item field, enter the desired parameter item. A list of values is available.
* The parameter items listed are those entered for this posting interface in program GPMM, Posting Parameter Item Maintenance.
* Depending on the parameter interface and the post type, the listed parameter items may or may not be able to be used. Click on one of the following links to view the NDS Standard parameter items that can be used for each post type and interface.
* Accounting for Commitments Post Types and Parameter Items*Accounting_for_Commitments_Post_Types_and_Parameter_Items
* Accounts Payable Post Types and Parameter Items*Accounts_Payable_Post_Types_and_Parameter_Items
* Bank Reconciliation Post Types and Parameter Items*Bank_Reconciliation_Post_Types_and_Parameters
* Fixed Asset Post Types and Parameter Items*Fixed_Assets_Post_Types_and_Parameters
* Manufacturing Post Types and Parameter Items*Manufacturing_Post_Types_and_Parameters
* Miscellaneous Application Post Types and Parameter Items*Miscellaneous_Application_Post_Types_and_Parameter_Items
* Project Tracking Post Types and Parameter Items*Project_Tracking_Post_Types_and_Parameter_Items
* Return Material Post Types and Parameter Items*Return_Material_Post_Types_and_Parameter_Items
* Sales Post Types and Parameter Items*Sales_Post_Types_and_Parameters
18. Set the Arg Op pop-list to the desired value. The argument operator expresses the relationship between the parameter item and the argument value.
* For an explanation of the values, see the SQL Language Reference Manual.
19. Enter the Argument Item or Value. For example, if this posting parameter record were for a specific customer class, that customer class would be entered in this field.
* If the value in this field is ANY, the Default flag will be set to on and the template will be considered a default posting parameter*Default_Posting_Parameter template.
20. Set the precedence if you have not already done so.
21. Press [Commit]. If you did not manually enter the sequence numbers, they will be assigned at this time by the system.
The information entered in this program for an abstract template can not be changed in program GPTE, Posting Template Value Entry. There are only three fields that can be altered in program GPTE, Posting Template Value Entry, the account numbers, the Argument Operator, and the Argument Item. These fields can only be changed only if certain conditions are met when the abstract template is set up in this program. The account number fields must be left blank, the Argument Operator must be set to ?, and the Argument Item field must have a ? in it.
1. The program opens in query mode. In the Posting Interface field, enter the posting interface for which you are entering abstract templates in the upper block of the program and press [Execute Query].
* Use the Sort By field to sort the templates displayed in the middle block. Choices are Template No and Score.
* To view existing posting parameter records, execute a query in the middle block of the program.
2. In the middle block, to add a new record, press the [New Record] button.
3. In the Template ID field, enter a unique template identifier.
* If you wish to copy the posting parameters from an existing template, enter the template identifier in the Copy From field, and press the [Copy] button.
* If you leave this field blank, a unique template ID will be generated when you commit.
4. In the Name field, enter a description for this template.
5. Set the template type pop-list to Abstract. This indicates to the program that this is a template that will be entered in program GPTE, Posting Template Value Entry.
* Setting this pop-list to Value Set indicates that the posting parameter record will be entered in program GPTM, Posting Template Maintenance.
6. The pop-list to the right of the Template Type pop-list indicates whether this posting type will generate postings or be posted to the general ledger.
* Select Post This if you wish postings of this type to be posted to the general ledger. Debit accounts and/or credit accounts will need to be assigned in program GPTE, Posting Template Value Entry, for any Posting Type with Post This next to it.
* Select Suppress to prevent a posting type from creating general ledger postings. No general ledger accounts are required in program GPTE, Posting Template Value Entry, when Suppress is next to the Posting Type.
7. In the Post Type pop-list, select the posting type for which you are creating an abstract template. At least one record must be created in either program GPTE, Posting Template Value Entry, or program GPTM, Posting Template Maintenance, for each posting type.
8. In the field to the right of the Post Type pop-list, enter a score value. The system, when searching for an account to which to post, uses the score to determine the order of the search.
* It will search through the posting parameter records in descending order by the value in the score field.
* A score with the value of 90 will be evaluated for matching parameters before a score with the vale of 10.
* When the system finds an exact match between the parameters and the transaction that it is trying to post, it takes that account numbers from that posting parameter record and looks no further.
9. Press [Commit]. Do not enter a debit or credit account in this program. The debit and credit account can be entered in program GPTE, Posting Template Value Entry.
10. In the lower block, enter the arguments that will be used to determine whether the posting will be made to the accounts that will be entered in GPTE, Posting Template Value Entry.
11. In the Seq field, you can assign a sequence number to each line. The sequence number determines where the parameter item is located in the SQL statement. Those with a lower sequence number will be placed first.
* If you do not assign a sequence number, it will be assigned when the record is committed.
* Those with a lower sequence number will be placed first.
12. Set the Precedence pop-list is used when generating the SQL statement from the information entered in the lower block. The precedence determines when, where, and how many parentheses will be placed in the SQL statement.
* A zero indicates that no parentheses will be placed. A one indicates that one set of parenthesis will be placed.
* The system will evaluate parameter items with a higher precedence before evaluating those with a lower precedence. If the parameter items are the same, they are evaluated from left to right in the SQL statement.
* For example, if the first parameter item has a precedence of zero, the second parameter item has a precedence of one, the third item has a precedence of one, and the fourth item has a precedence of zero, then a single parentheses will be placed around the first, second, and third items, but not the fourth.
13. In the Link Op pop-list, select the link operator for the posting parameter record.
* The first Link Operator must be a WHERE statement.
* Each Link Operator that follows the first link operator connects the parameter item to the parameter item before it.
* For explanations of the AND and OR Link Operators, see the SQL Language Reference Manual.
14. In the Parameter Item field, enter the desired parameter item. A list of values is available.
* The parameter items listed are those entered for this posting interface in program GPMM, Posting Parameter Item Maintenance.
* Depending on the parameter interface and the post type, the listed parameter items may or may not be able to be used. Click on one of the following links to view the NDS Standard parameter items that can be used for each post type and interface.
* Accounting for Commitments Post Types and Parameter Items*Accounting_for_Commitments_Post_Types_and_Parameter_Items
* Accounts Payable Post Types and Parameter Items*Accounts_Payable_Post_Types_and_Parameter_Items
* Bank Reconciliation Post Types and Parameter Items*Bank_Reconciliation_Post_Types_and_Parameters
* Fixed Asset Post Types and Parameter Items*Fixed_Assets_Post_Types_and_Parameters
* Manufacturing Post Types and Parameter Items*Manufacturing_Post_Types_and_Parameters
* Miscellaneous Application Post Types and Parameter Items*Miscellaneous_Application_Post_Types_and_Parameter_Items
* Project Tracking Post Types and Parameter Items*Project_Tracking_Post_Types_and_Parameter_Items
* Return Material Post Types and Parameter Items*Return_Material_Post_Types_and_Parameter_Items
* Sales Post Types and Parameter Items*Sales_Post_Types_and_Parameters
15. Set the Arg Op pop-list to the desired value. The argument operator expresses the relationship between the parameter item and the argument value.
* For an explanation of the values, see the SQL Language Reference Manual.
* If the Argument Operator will be changed in program GPTE, Posting Template Value Entry, set it to a ? in this program.
16. In the Argument Item or Value field, enter a ?. This will allow the value to be changed in program GPTE, Posting Template Value Entry.
17. Set the precedence if you have not already done so.
18. Press [Commit]. If you did not manually enter the sequence numbers, they will be assigned at this time by the system.
19. Go to program GPTE, Posting Template Value Entry, to enter the posting parameter records.
Press this button to copy the posting parameter record entered in the Copy From field.
On the summary screen, press this button to query this posting interface and type.
Press this button to view additional information by posting interface/type. Information includes the interface, post type, name, value template count, default template count, and any messages.