DelBatchHeader

F48011 Billing Batch Validation

Minor Business Rule

Object Name: N48S0290

Parent DLL: CCRIN

Location: Client/Server

Language: NER

Data Structure

D48S0290 - Billing Batch Validation

Parameter Name	Data Item	Data Type	Req/Opt	I/O/Both
cBatchTypeServBill	BCTY	char	REQ	INPUT
A code that specifies whether the batch is from the Service Billing system or the Contract Billing system. Valid values are: 3 Service Billing 4 Contract Billing For Contract Billing Revenue processing, the batch type is always 3.
mnBatchNumber	ICU	MATH_NUMERIC	REQ	INPUT
A number that identifies a group of transactions that the system processes and balances as a unit. When you enter a batch, you can either assign a batch number or let the system assign it using the Next Numbers program.
cGenerationTypeService	GTYP	char	OPT	INPUT
A code that determines the batch types and markup rules for invoice, revenue, and component amounts. The system assigns the batch type when the batch is created. Depending on how you define the billing constants, different markup rules can apply to different amounts. Valid values are: 1 Apply the markup rule to invoice, revenue, and component amounts. If the billing constants specify that invoice and revenue amounts are always the same, the markup rule applies to revenue, invoice, and component amounts. If the billing constants specify that the invoice and revenue amounts can be different, the markup rule still applies to revenue, invoice, and component amounts if no type 2 rule exists. 2 Apply the markup rule to revenue and component amounts. If the billing constants specify that the invoice and revenue amounts can be different, the markup rule applies to revenue and component amounts only. 3 Apply the markup rule to component amounts only. This rule is not dependent on billing constants settings.
cBatchStatusDescription	BS	char	OPT	INPUT
A control function in the Service Billing and Contract Billing systems. The system verifies the following values prior to executing various jobs to ensure the functions are performed in the proper sequence. Valid values are: blank Invoices have not been created 0 Manual adjustment in Contract Billing 1 Invoices generated without errors 2 Invoices generated with errors 3 Revenue journals created without errors 4 Revenue journals created with errors 5 Invoice journals created without errors 6 Invoice journals created with errors 7 Batch changed - rerun journals 8 Active revenue batch found Batch status descriptions are stored in UDC 48/BS.
cCurrentActivity	CUAC	char	OPT	INPUT
Identifies the processing cycle step that is currently active. This field maintains the integrity of the batch member throughout the Service Billing and Contract Billing systems. The Batch Revisions form uses this field to ensure that the Batch Number selected is qualified for a particular function. Valid values are: 0 Available 1 Generation in process 2 Maintenance in process 3 Journal generation in process 4 Batch delete in process 5 Invoice printing in process 6 Batch posting 7 Selection in progress * Display all batches (World Only)
mnAmountEntered	AME	MATH_NUMERIC	OPT	INPUT
The total amount of transactions entered.
mnAmountDocumentsEntered	DOCN	MATH_NUMERIC	OPT	INPUT
If you are using the batch control feature, the number of transactions entered into the batch. If you are not using batch control, the system displays the number as negative. Note: The batch review screen is used by many J.D. Edwards systems. As a result, this field might not apply to batches created by your particular system.
jdDateBatchJulian	DICJ	JDEDATE	OPT	INPUT
The date of the batch. If you leave this field blank, the system date is used.
jdDtForGLAndVouch1	DGL	JDEDATE	OPT	INPUT
A date that identifies the financial period to which the transaction is to be posted. The company constants specify the date range for each financial period. You can have as many as 14 periods. Generally, period 14 is used for audit adjustments. The system validates this field for PBCO (posted before cutoff), PYEB (prior year ending balance), PACO (post after cutoff), and WACO (post way after cutoff) messages.
jdDateBillFrom	BTFR	JDEDATE	OPT	INPUT
The from date used to determine if a transaction is billed. The transaction is billed if the general ledger date falls between the from date and the through date.
mnBatchNumberJournal	ICUJ	MATH_NUMERIC	OPT	INPUT
A batch number the system automatically assigns when you run Revenue Journal Generation.
mnAmountRevenueJournal	AMEJ	MATH_NUMERIC	OPT	INPUT
The total amount of transactions included in this batch of revenue journals.
mnAmountDocumentsEnter	DOCJ	MATH_NUMERIC	OPT	INPUT
The total number of transactions included in this batch of revenue journals.
mnBatchNumberActive	ICUA	MATH_NUMERIC	OPT	INPUT
This is the batch number assigned during the Service Billing generation. This batch number will be used as a linking mechanism to allow the user to reset records in the Service Billing History file (F4812H) to their previous journal status. This field will contain a batch number only while the batch is recognized by the system as being active and hasn't been posted. This field can be cleared at two possible times during the Service Billing Generation cycle; either when the batch is identified for deletion or if the batch is posted.
cRevenueJournalsGenerated	RGEN	char	OPT	INPUT
This field is used to identify whether a batch of revenue journals have been processed for this batch of invoices. If revenue journals have been created,then this batch is ineligible for deletion within the Contract Billing system. The valid values are: 0 Revenue Journals have not been created. 1 Revenue Journals have been created.
cContrlFlag1	BCT1	char	OPT	INPUT
An option that specifies whether the system performs Not-To-Exceed (NTE) processing for Contract Billing. Turn on this option to perform NTE processing.
cControlFlag2	BCT2	char	OPT	INPUT
A generic control flag reserved for future use within the Service Billing Batch Header File (F48011).
cControlFlag3	BCT3	char	OPT	INPUT
A generic control flag reserved for future use within the Service Billing Batch Header File (F48011).
cControlFlag4	BCT4	char	OPT	INPUT
A generic control flag reserved for future use within the Service Billing Batch Header File (F48011).
cControlFlag5	BCT5	char	OPT	INPUT
A generic control flag reserved for future use within the Service Billing Batch Header File (F48011).
szBatchControlKey	BCTK	char	OPT	INPUT
Reserved by J.D. Edwards.
szBatchControl	BCTC	char	OPT	INPUT
Future Use
cBatchApprovedForPost	IAPP	char	OPT	INPUT
An option that indicates whether a batch is approved and ready for posting, or whether it is pending approval. You may select only one option. They are: o Approved for posting o Pending approval. The batch will not post. If the system constants do not specify manager approval, the system automatically approves batches that are not in error.
szAuthorizedUserId	AUSR	char	OPT	INPUT
Authorized User ID
szUserId	USER	char	OPT	INPUT
The code that identifies a user profile.
szWorkStationId	JOBN	char	OPT	INPUT
The code that identifies the work station ID that executed a particular job.
jdDateUpdated	UPMJ	JDEDATE	OPT	INPUT
The date that specifies the last update to the file record.
mnTimeLastUpdated	UPMT	MATH_NUMERIC	OPT	INPUT
The time that specifies when the program executed the last update to this record.
szDocTypeInvoiceOnly	DCTI	char	OPT	INPUT
A user defined (00/DI) document type for invoice entry. Any document type set up for invoice-only entry should begin with the letter R (receivables). The default is RI, RR, or RM. Reserved document types have been defined for vouchers, invoices, receipts, and time sheets. The reserved document types are: P_ Accounts Payable Documents R_Accounts Receivable Documents T_ Payroll Documents I_Inventory Documents O_ Order Processing Documents Note: Verify that the default document type for invoices is set up in both UDC 00/DT and UDC 00/DI.
szDocumentCompanyInvoice	KCOI	char	OPT	INPUT
Invoice Document Company.
mnDocumentOrderAlt	DOCZ	MATH_NUMERIC	OPT	INPUT
The original document number. This can be a voucher, an invoice, unapplied cash, a journal entry number, etc. Matching document numbers are also used to identify related documents in the Accounts Receivable and Accounts Payable systems. See matching document (DOCM). This document number (DOCO) is always the original document number, and the matching document number (DOCM) is the check, adjustment, or credit to be applied against the original document. For example: A/P Automated/Manual Payment: Original (DOCO) - Voucher; Matching Document (DOCM) - Payment A/R Original Invoice: Original (DOCO) - Invoice Receipt Application: Original (DOCO) - Invoice; Matching Document (DOCM) - Receipt Credit Memo/Adjustment: Original (DOCO) - Invoice; Matching Document (DOCM) -Credit Memo Unapplied Case: Original (DOCO) - Receipt
szDocumentPayItem	SFX	char	OPT	INPUT
A number that identifies the pay item for a voucher or an invoice. The system assigns the pay item number. If the voucher or invoice has multiple pay items, the numbers are sequential.
szProgramId	PID	char	OPT	INPUT
The number that identifies the batch or interactive program (batch or interactive object). For example, the number of the Sales Order Entry interactive program is P4210, and the number of the Print Invoices batch process report is R42565. The program ID is a variable length value. It is assigned according to a structured syntax in the form TSSXXX, where: T The first character of the number is alphabetic and identifies the type, such as P for Program, R for Report, and so on. For example, the value P in the number P4210 indicates that the object is a program. SS The second and third characters of the number are numeric and identify the system code. For example, the value 42 in the number P4210 indicates that this program belongs to system 42, which is the Sales Order Processing system. XXX The remaining characters of the numer are numeric and identify a unique program or report. For example, the value 10 in the number P4210 indicates that this is the Sales Order Entry program.
cUpdateFlag	EV01	char	OPT	INPUT
An option that specifies the type of processing for an event.
szBatchType	ICUT	char	OPT	INPUT
A code that specifies the system and type of transactions entered in a batch. The system assigns the value when you enter a transaction. Valid values are set up in user defined code table 98/IT. You cannot assign new values. All batch types are hard coded.

Related Functions

None

Related Tables

None

GetBatchHeaderInforation

F48011 Billing Batch Validation

Minor Business Rule

Object Name: N48S0290

Parent DLL: CCRIN

Location: Client/Server

Language: NER

Data Structure

D48S0290A - Billing Batch Control Information

Parameter Name	Data Item	Data Type	Req/Opt	I/O/Both
mnBatchNumber	ICU	MATH_NUMERIC	REQ	INPUT
A number that identifies a group of transactions that the system processes and balances as a unit. When you enter a batch, you can either assign a batch number or let the system assign it using the Next Numbers program.
cBatchTypeServBill	BCTY	char	OPT	BOTH
A code that specifies whether the batch is from the Service Billing system or the Contract Billing system. Valid values are: 3 Service Billing 4 Contract Billing For Contract Billing Revenue processing, the batch type is always 3.
cBatchStatusDescription	BS	char	OPT	OUTPUT
A control function in the Service Billing and Contract Billing systems. The system verifies the following values prior to executing various jobs to ensure the functions are performed in the proper sequence. Valid values are: blank Invoices have not been created 0 Manual adjustment in Contract Billing 1 Invoices generated without errors 2 Invoices generated with errors 3 Revenue journals created without errors 4 Revenue journals created with errors 5 Invoice journals created without errors 6 Invoice journals created with errors 7 Batch changed - rerun journals 8 Active revenue batch found Batch status descriptions are stored in UDC 48/BS.
cCurrentActivity	CUAC	char	OPT	OUTPUT
Identifies the processing cycle step that is currently active. This field maintains the integrity of the batch member throughout the Service Billing and Contract Billing systems. The Batch Revisions form uses this field to ensure that the Batch Number selected is qualified for a particular function. Valid values are: 0 Available 1 Generation in process 2 Maintenance in process 3 Journal generation in process 4 Batch delete in process 5 Invoice printing in process 6 Batch posting 7 Selection in progress * Display all batches (World Only)
mnAmountEntered	AME	MATH_NUMERIC	OPT	OUTPUT
The total amount of transactions entered.
mnAmountDocumentsEntered	DOCN	MATH_NUMERIC	OPT	OUTPUT
If you are using the batch control feature, the number of transactions entered into the batch. If you are not using batch control, the system displays the number as negative. Note: The batch review screen is used by many J.D. Edwards systems. As a result, this field might not apply to batches created by your particular system.
jdDateBatchJulian	DICJ	JDEDATE	OPT	OUTPUT
The date of the batch. If you leave this field blank, the system date is used.
cGenerationTypeService	GTYP	char	OPT	BOTH
A code that determines the batch types and markup rules for invoice, revenue, and component amounts. The system assigns the batch type when the batch is created. Depending on how you define the billing constants, different markup rules can apply to different amounts. Valid values are: 1 Apply the markup rule to invoice, revenue, and component amounts. If the billing constants specify that invoice and revenue amounts are always the same, the markup rule applies to revenue, invoice, and component amounts. If the billing constants specify that the invoice and revenue amounts can be different, the markup rule still applies to revenue, invoice, and component amounts if no type 2 rule exists. 2 Apply the markup rule to revenue and component amounts. If the billing constants specify that the invoice and revenue amounts can be different, the markup rule applies to revenue and component amounts only. 3 Apply the markup rule to component amounts only. This rule is not dependent on billing constants settings.
jdDtForGLAndVouch1	DGL	JDEDATE	OPT	OUTPUT
A date that identifies the financial period to which the transaction is to be posted. The company constants specify the date range for each financial period. You can have as many as 14 periods. Generally, period 14 is used for audit adjustments. The system validates this field for PBCO (posted before cutoff), PYEB (prior year ending balance), PACO (post after cutoff), and WACO (post way after cutoff) messages.
jdDateBillFrom	BTFR	JDEDATE	OPT	OUTPUT
The from date used to determine if a transaction is billed. The transaction is billed if the general ledger date falls between the from date and the through date.
mnBatchNumberJournal	ICUJ	MATH_NUMERIC	OPT	OUTPUT
A batch number the system automatically assigns when you run Revenue Journal Generation.
mnAmountRevenueJournal	AMEJ	MATH_NUMERIC	OPT	OUTPUT
The total amount of transactions included in this batch of revenue journals.
mnAmountDocumentsEnter	DOCJ	MATH_NUMERIC	OPT	OUTPUT
The total number of transactions included in this batch of revenue journals.
cRevenueJournalsGenerated	RGEN	char	OPT	OUTPUT
This field is used to identify whether a batch of revenue journals have been processed for this batch of invoices. If revenue journals have been created,then this batch is ineligible for deletion within the Contract Billing system. The valid values are: 0 Revenue Journals have not been created. 1 Revenue Journals have been created.
mnBatchNumberActive	ICUA	MATH_NUMERIC	OPT	OUTPUT
This is the batch number assigned during the Service Billing generation. This batch number will be used as a linking mechanism to allow the user to reset records in the Service Billing History file (F4812H) to their previous journal status. This field will contain a batch number only while the batch is recognized by the system as being active and hasn't been posted. This field can be cleared at two possible times during the Service Billing Generation cycle; either when the batch is identified for deletion or if the batch is posted.
cContrlFlag1	BCT1	char	OPT	OUTPUT
An option that specifies whether the system performs Not-To-Exceed (NTE) processing for Contract Billing. Turn on this option to perform NTE processing.
cControlFlag2	BCT2	char	OPT	OUTPUT
A generic control flag reserved for future use within the Service Billing Batch Header File (F48011).
cControlFlag3	BCT3	char	OPT	OUTPUT
A generic control flag reserved for future use within the Service Billing Batch Header File (F48011).
cControlFlag4	BCT4	char	OPT	OUTPUT
A generic control flag reserved for future use within the Service Billing Batch Header File (F48011).
cControlFlag5	BCT5	char	OPT	OUTPUT
A generic control flag reserved for future use within the Service Billing Batch Header File (F48011).
szBatchControlKey	BCTK	char	OPT	OUTPUT
Reserved by J.D. Edwards.
szBatchControl	BCTC	char	OPT	OUTPUT
Future Use
cBatchApprovedForPost	IAPP	char	OPT	OUTPUT
An option that indicates whether a batch is approved and ready for posting, or whether it is pending approval. You may select only one option. They are: o Approved for posting o Pending approval. The batch will not post. If the system constants do not specify manager approval, the system automatically approves batches that are not in error.
szAuthorizedUserId	AUSR	char	OPT	OUTPUT
Authorized User ID
szUserId	USER	char	OPT	OUTPUT
The code that identifies a user profile.
szWorkStationId	JOBN	char	OPT	OUTPUT
The code that identifies the work station ID that executed a particular job.
szProgramId	PID	char	OPT	OUTPUT
The number that identifies the batch or interactive program (batch or interactive object). For example, the number of the Sales Order Entry interactive program is P4210, and the number of the Print Invoices batch process report is R42565. The program ID is a variable length value. It is assigned according to a structured syntax in the form TSSXXX, where: T The first character of the number is alphabetic and identifies the type, such as P for Program, R for Report, and so on. For example, the value P in the number P4210 indicates that the object is a program. SS The second and third characters of the number are numeric and identify the system code. For example, the value 42 in the number P4210 indicates that this program belongs to system 42, which is the Sales Order Processing system. XXX The remaining characters of the numer are numeric and identify a unique program or report. For example, the value 10 in the number P4210 indicates that this is the Sales Order Entry program.
jdDateUpdated	UPMJ	JDEDATE	OPT	OUTPUT
The date that specifies the last update to the file record.
mnTimeLastUpdated	UPMT	MATH_NUMERIC	OPT	OUTPUT
The time that specifies when the program executed the last update to this record.

Related Functions

None

Related Tables

None

UpdateBatchAmtsDocs

F48011 Billing Batch Validation

Minor Business Rule

Object Name: N48S0290

Parent DLL: CCRIN

Location: Client/Server

Language: NER

Use the Update Flag to determine which fields in the Batch Header are to be updated. The values for
Update Flag are:
1 = Current Activity
2 = Batch Status
3 = Current Activity and Batch Status
4 = Current Activity, Batch Status, Number of Documents and Batch Amount.
^

Data Structure

D48S0290 - Billing Batch Validation

Parameter Name	Data Item	Data Type	Req/Opt	I/O/Both
cBatchTypeServBill	BCTY	char	REQ	INPUT
A code that specifies whether the batch is from the Service Billing system or the Contract Billing system. Valid values are: 3 Service Billing 4 Contract Billing For Contract Billing Revenue processing, the batch type is always 3.
mnBatchNumber	ICU	MATH_NUMERIC	REQ	INPUT
A number that identifies a group of transactions that the system processes and balances as a unit. When you enter a batch, you can either assign a batch number or let the system assign it using the Next Numbers program.
cGenerationTypeService	GTYP	char	OPT	INPUT
A code that determines the batch types and markup rules for invoice, revenue, and component amounts. The system assigns the batch type when the batch is created. Depending on how you define the billing constants, different markup rules can apply to different amounts. Valid values are: 1 Apply the markup rule to invoice, revenue, and component amounts. If the billing constants specify that invoice and revenue amounts are always the same, the markup rule applies to revenue, invoice, and component amounts. If the billing constants specify that the invoice and revenue amounts can be different, the markup rule still applies to revenue, invoice, and component amounts if no type 2 rule exists. 2 Apply the markup rule to revenue and component amounts. If the billing constants specify that the invoice and revenue amounts can be different, the markup rule applies to revenue and component amounts only. 3 Apply the markup rule to component amounts only. This rule is not dependent on billing constants settings.
cBatchStatusDescription	BS	char	OPT	INPUT
A control function in the Service Billing and Contract Billing systems. The system verifies the following values prior to executing various jobs to ensure the functions are performed in the proper sequence. Valid values are: blank Invoices have not been created 0 Manual adjustment in Contract Billing 1 Invoices generated without errors 2 Invoices generated with errors 3 Revenue journals created without errors 4 Revenue journals created with errors 5 Invoice journals created without errors 6 Invoice journals created with errors 7 Batch changed - rerun journals 8 Active revenue batch found Batch status descriptions are stored in UDC 48/BS.
cCurrentActivity	CUAC	char	OPT	INPUT
Identifies the processing cycle step that is currently active. This field maintains the integrity of the batch member throughout the Service Billing and Contract Billing systems. The Batch Revisions form uses this field to ensure that the Batch Number selected is qualified for a particular function. Valid values are: 0 Available 1 Generation in process 2 Maintenance in process 3 Journal generation in process 4 Batch delete in process 5 Invoice printing in process 6 Batch posting 7 Selection in progress * Display all batches (World Only)
mnAmountEntered	AME	MATH_NUMERIC	OPT	INPUT
The total amount of transactions entered.
mnAmountDocumentsEntered	DOCN	MATH_NUMERIC	OPT	INPUT
If you are using the batch control feature, the number of transactions entered into the batch. If you are not using batch control, the system displays the number as negative. Note: The batch review screen is used by many J.D. Edwards systems. As a result, this field might not apply to batches created by your particular system.
jdDateBatchJulian	DICJ	JDEDATE	OPT	INPUT
The date of the batch. If you leave this field blank, the system date is used.
jdDtForGLAndVouch1	DGL	JDEDATE	OPT	INPUT
A date that identifies the financial period to which the transaction is to be posted. The company constants specify the date range for each financial period. You can have as many as 14 periods. Generally, period 14 is used for audit adjustments. The system validates this field for PBCO (posted before cutoff), PYEB (prior year ending balance), PACO (post after cutoff), and WACO (post way after cutoff) messages.
jdDateBillFrom	BTFR	JDEDATE	OPT	INPUT
The from date used to determine if a transaction is billed. The transaction is billed if the general ledger date falls between the from date and the through date.
mnBatchNumberJournal	ICUJ	MATH_NUMERIC	OPT	INPUT
A batch number the system automatically assigns when you run Revenue Journal Generation.
mnAmountRevenueJournal	AMEJ	MATH_NUMERIC	OPT	INPUT
The total amount of transactions included in this batch of revenue journals.
mnAmountDocumentsEnter	DOCJ	MATH_NUMERIC	OPT	INPUT
The total number of transactions included in this batch of revenue journals.
mnBatchNumberActive	ICUA	MATH_NUMERIC	OPT	INPUT
This is the batch number assigned during the Service Billing generation. This batch number will be used as a linking mechanism to allow the user to reset records in the Service Billing History file (F4812H) to their previous journal status. This field will contain a batch number only while the batch is recognized by the system as being active and hasn't been posted. This field can be cleared at two possible times during the Service Billing Generation cycle; either when the batch is identified for deletion or if the batch is posted.
cRevenueJournalsGenerated	RGEN	char	OPT	INPUT
This field is used to identify whether a batch of revenue journals have been processed for this batch of invoices. If revenue journals have been created,then this batch is ineligible for deletion within the Contract Billing system. The valid values are: 0 Revenue Journals have not been created. 1 Revenue Journals have been created.
cContrlFlag1	BCT1	char	OPT	INPUT
An option that specifies whether the system performs Not-To-Exceed (NTE) processing for Contract Billing. Turn on this option to perform NTE processing.
cControlFlag2	BCT2	char	OPT	INPUT
A generic control flag reserved for future use within the Service Billing Batch Header File (F48011).
cControlFlag3	BCT3	char	OPT	INPUT
A generic control flag reserved for future use within the Service Billing Batch Header File (F48011).
cControlFlag4	BCT4	char	OPT	INPUT
A generic control flag reserved for future use within the Service Billing Batch Header File (F48011).
cControlFlag5	BCT5	char	OPT	INPUT
A generic control flag reserved for future use within the Service Billing Batch Header File (F48011).
szBatchControlKey	BCTK	char	OPT	INPUT
Reserved by J.D. Edwards.
szBatchControl	BCTC	char	OPT	INPUT
Future Use
cBatchApprovedForPost	IAPP	char	OPT	INPUT
An option that indicates whether a batch is approved and ready for posting, or whether it is pending approval. You may select only one option. They are: o Approved for posting o Pending approval. The batch will not post. If the system constants do not specify manager approval, the system automatically approves batches that are not in error.
szAuthorizedUserId	AUSR	char	OPT	INPUT
Authorized User ID
szUserId	USER	char	OPT	INPUT
The code that identifies a user profile.
szWorkStationId	JOBN	char	OPT	INPUT
The code that identifies the work station ID that executed a particular job.
jdDateUpdated	UPMJ	JDEDATE	OPT	INPUT
The date that specifies the last update to the file record.
mnTimeLastUpdated	UPMT	MATH_NUMERIC	OPT	INPUT
The time that specifies when the program executed the last update to this record.
szDocTypeInvoiceOnly	DCTI	char	OPT	INPUT
A user defined (00/DI) document type for invoice entry. Any document type set up for invoice-only entry should begin with the letter R (receivables). The default is RI, RR, or RM. Reserved document types have been defined for vouchers, invoices, receipts, and time sheets. The reserved document types are: P_ Accounts Payable Documents R_Accounts Receivable Documents T_ Payroll Documents I_Inventory Documents O_ Order Processing Documents Note: Verify that the default document type for invoices is set up in both UDC 00/DT and UDC 00/DI.
szDocumentCompanyInvoice	KCOI	char	OPT	INPUT
Invoice Document Company.
mnDocumentOrderAlt	DOCZ	MATH_NUMERIC	OPT	INPUT
The original document number. This can be a voucher, an invoice, unapplied cash, a journal entry number, etc. Matching document numbers are also used to identify related documents in the Accounts Receivable and Accounts Payable systems. See matching document (DOCM). This document number (DOCO) is always the original document number, and the matching document number (DOCM) is the check, adjustment, or credit to be applied against the original document. For example: A/P Automated/Manual Payment: Original (DOCO) - Voucher; Matching Document (DOCM) - Payment A/R Original Invoice: Original (DOCO) - Invoice Receipt Application: Original (DOCO) - Invoice; Matching Document (DOCM) - Receipt Credit Memo/Adjustment: Original (DOCO) - Invoice; Matching Document (DOCM) -Credit Memo Unapplied Case: Original (DOCO) - Receipt
szDocumentPayItem	SFX	char	OPT	INPUT
A number that identifies the pay item for a voucher or an invoice. The system assigns the pay item number. If the voucher or invoice has multiple pay items, the numbers are sequential.
szProgramId	PID	char	OPT	INPUT
The number that identifies the batch or interactive program (batch or interactive object). For example, the number of the Sales Order Entry interactive program is P4210, and the number of the Print Invoices batch process report is R42565. The program ID is a variable length value. It is assigned according to a structured syntax in the form TSSXXX, where: T The first character of the number is alphabetic and identifies the type, such as P for Program, R for Report, and so on. For example, the value P in the number P4210 indicates that the object is a program. SS The second and third characters of the number are numeric and identify the system code. For example, the value 42 in the number P4210 indicates that this program belongs to system 42, which is the Sales Order Processing system. XXX The remaining characters of the numer are numeric and identify a unique program or report. For example, the value 10 in the number P4210 indicates that this is the Sales Order Entry program.
cUpdateFlag	EV01	char	OPT	INPUT
An option that specifies the type of processing for an event.
szBatchType	ICUT	char	OPT	INPUT
A code that specifies the system and type of transactions entered in a batch. The system assigns the value when you enter a transaction. Valid values are set up in user defined code table 98/IT. You cannot assign new values. All batch types are hard coded.

Related Functions

None

Related Tables

None

WriteBatchHeader

F48011 Billing Batch Validation

Minor Business Rule

Object Name: N48S0290

Parent DLL: CCRIN

Location: Client/Server

Language: NER

Data Structure

D48S0290 - Billing Batch Validation

Parameter Name	Data Item	Data Type	Req/Opt	I/O/Both
cBatchTypeServBill	BCTY	char	REQ	INPUT
A code that specifies whether the batch is from the Service Billing system or the Contract Billing system. Valid values are: 3 Service Billing 4 Contract Billing For Contract Billing Revenue processing, the batch type is always 3.
mnBatchNumber	ICU	MATH_NUMERIC	REQ	INPUT
A number that identifies a group of transactions that the system processes and balances as a unit. When you enter a batch, you can either assign a batch number or let the system assign it using the Next Numbers program.
cGenerationTypeService	GTYP	char	OPT	INPUT
A code that determines the batch types and markup rules for invoice, revenue, and component amounts. The system assigns the batch type when the batch is created. Depending on how you define the billing constants, different markup rules can apply to different amounts. Valid values are: 1 Apply the markup rule to invoice, revenue, and component amounts. If the billing constants specify that invoice and revenue amounts are always the same, the markup rule applies to revenue, invoice, and component amounts. If the billing constants specify that the invoice and revenue amounts can be different, the markup rule still applies to revenue, invoice, and component amounts if no type 2 rule exists. 2 Apply the markup rule to revenue and component amounts. If the billing constants specify that the invoice and revenue amounts can be different, the markup rule applies to revenue and component amounts only. 3 Apply the markup rule to component amounts only. This rule is not dependent on billing constants settings.
cBatchStatusDescription	BS	char	OPT	INPUT
A control function in the Service Billing and Contract Billing systems. The system verifies the following values prior to executing various jobs to ensure the functions are performed in the proper sequence. Valid values are: blank Invoices have not been created 0 Manual adjustment in Contract Billing 1 Invoices generated without errors 2 Invoices generated with errors 3 Revenue journals created without errors 4 Revenue journals created with errors 5 Invoice journals created without errors 6 Invoice journals created with errors 7 Batch changed - rerun journals 8 Active revenue batch found Batch status descriptions are stored in UDC 48/BS.
cCurrentActivity	CUAC	char	OPT	INPUT
Identifies the processing cycle step that is currently active. This field maintains the integrity of the batch member throughout the Service Billing and Contract Billing systems. The Batch Revisions form uses this field to ensure that the Batch Number selected is qualified for a particular function. Valid values are: 0 Available 1 Generation in process 2 Maintenance in process 3 Journal generation in process 4 Batch delete in process 5 Invoice printing in process 6 Batch posting 7 Selection in progress * Display all batches (World Only)
mnAmountEntered	AME	MATH_NUMERIC	OPT	INPUT
The total amount of transactions entered.
mnAmountDocumentsEntered	DOCN	MATH_NUMERIC	OPT	INPUT
If you are using the batch control feature, the number of transactions entered into the batch. If you are not using batch control, the system displays the number as negative. Note: The batch review screen is used by many J.D. Edwards systems. As a result, this field might not apply to batches created by your particular system.
jdDateBatchJulian	DICJ	JDEDATE	OPT	INPUT
The date of the batch. If you leave this field blank, the system date is used.
jdDtForGLAndVouch1	DGL	JDEDATE	OPT	INPUT
A date that identifies the financial period to which the transaction is to be posted. The company constants specify the date range for each financial period. You can have as many as 14 periods. Generally, period 14 is used for audit adjustments. The system validates this field for PBCO (posted before cutoff), PYEB (prior year ending balance), PACO (post after cutoff), and WACO (post way after cutoff) messages.
jdDateBillFrom	BTFR	JDEDATE	OPT	INPUT
The from date used to determine if a transaction is billed. The transaction is billed if the general ledger date falls between the from date and the through date.
mnBatchNumberJournal	ICUJ	MATH_NUMERIC	OPT	INPUT
A batch number the system automatically assigns when you run Revenue Journal Generation.
mnAmountRevenueJournal	AMEJ	MATH_NUMERIC	OPT	INPUT
The total amount of transactions included in this batch of revenue journals.
mnAmountDocumentsEnter	DOCJ	MATH_NUMERIC	OPT	INPUT
The total number of transactions included in this batch of revenue journals.
mnBatchNumberActive	ICUA	MATH_NUMERIC	OPT	INPUT
This is the batch number assigned during the Service Billing generation. This batch number will be used as a linking mechanism to allow the user to reset records in the Service Billing History file (F4812H) to their previous journal status. This field will contain a batch number only while the batch is recognized by the system as being active and hasn't been posted. This field can be cleared at two possible times during the Service Billing Generation cycle; either when the batch is identified for deletion or if the batch is posted.
cRevenueJournalsGenerated	RGEN	char	OPT	INPUT
This field is used to identify whether a batch of revenue journals have been processed for this batch of invoices. If revenue journals have been created,then this batch is ineligible for deletion within the Contract Billing system. The valid values are: 0 Revenue Journals have not been created. 1 Revenue Journals have been created.
cContrlFlag1	BCT1	char	OPT	INPUT
An option that specifies whether the system performs Not-To-Exceed (NTE) processing for Contract Billing. Turn on this option to perform NTE processing.
cControlFlag2	BCT2	char	OPT	INPUT
A generic control flag reserved for future use within the Service Billing Batch Header File (F48011).
cControlFlag3	BCT3	char	OPT	INPUT
A generic control flag reserved for future use within the Service Billing Batch Header File (F48011).
cControlFlag4	BCT4	char	OPT	INPUT
A generic control flag reserved for future use within the Service Billing Batch Header File (F48011).
cControlFlag5	BCT5	char	OPT	INPUT
A generic control flag reserved for future use within the Service Billing Batch Header File (F48011).
szBatchControlKey	BCTK	char	OPT	INPUT
Reserved by J.D. Edwards.
szBatchControl	BCTC	char	OPT	INPUT
Future Use
cBatchApprovedForPost	IAPP	char	OPT	INPUT
An option that indicates whether a batch is approved and ready for posting, or whether it is pending approval. You may select only one option. They are: o Approved for posting o Pending approval. The batch will not post. If the system constants do not specify manager approval, the system automatically approves batches that are not in error.
szAuthorizedUserId	AUSR	char	OPT	INPUT
Authorized User ID
szUserId	USER	char	OPT	INPUT
The code that identifies a user profile.
szWorkStationId	JOBN	char	OPT	INPUT
The code that identifies the work station ID that executed a particular job.
jdDateUpdated	UPMJ	JDEDATE	OPT	INPUT
The date that specifies the last update to the file record.
mnTimeLastUpdated	UPMT	MATH_NUMERIC	OPT	INPUT
The time that specifies when the program executed the last update to this record.
szDocTypeInvoiceOnly	DCTI	char	OPT	INPUT
A user defined (00/DI) document type for invoice entry. Any document type set up for invoice-only entry should begin with the letter R (receivables). The default is RI, RR, or RM. Reserved document types have been defined for vouchers, invoices, receipts, and time sheets. The reserved document types are: P_ Accounts Payable Documents R_Accounts Receivable Documents T_ Payroll Documents I_Inventory Documents O_ Order Processing Documents Note: Verify that the default document type for invoices is set up in both UDC 00/DT and UDC 00/DI.
szDocumentCompanyInvoice	KCOI	char	OPT	INPUT
Invoice Document Company.
mnDocumentOrderAlt	DOCZ	MATH_NUMERIC	OPT	INPUT
The original document number. This can be a voucher, an invoice, unapplied cash, a journal entry number, etc. Matching document numbers are also used to identify related documents in the Accounts Receivable and Accounts Payable systems. See matching document (DOCM). This document number (DOCO) is always the original document number, and the matching document number (DOCM) is the check, adjustment, or credit to be applied against the original document. For example: A/P Automated/Manual Payment: Original (DOCO) - Voucher; Matching Document (DOCM) - Payment A/R Original Invoice: Original (DOCO) - Invoice Receipt Application: Original (DOCO) - Invoice; Matching Document (DOCM) - Receipt Credit Memo/Adjustment: Original (DOCO) - Invoice; Matching Document (DOCM) -Credit Memo Unapplied Case: Original (DOCO) - Receipt
szDocumentPayItem	SFX	char	OPT	INPUT
A number that identifies the pay item for a voucher or an invoice. The system assigns the pay item number. If the voucher or invoice has multiple pay items, the numbers are sequential.
szProgramId	PID	char	OPT	INPUT
The number that identifies the batch or interactive program (batch or interactive object). For example, the number of the Sales Order Entry interactive program is P4210, and the number of the Print Invoices batch process report is R42565. The program ID is a variable length value. It is assigned according to a structured syntax in the form TSSXXX, where: T The first character of the number is alphabetic and identifies the type, such as P for Program, R for Report, and so on. For example, the value P in the number P4210 indicates that the object is a program. SS The second and third characters of the number are numeric and identify the system code. For example, the value 42 in the number P4210 indicates that this program belongs to system 42, which is the Sales Order Processing system. XXX The remaining characters of the numer are numeric and identify a unique program or report. For example, the value 10 in the number P4210 indicates that this is the Sales Order Entry program.
cUpdateFlag	EV01	char	OPT	INPUT
An option that specifies the type of processing for an event.
szBatchType	ICUT	char	OPT	INPUT
A code that specifies the system and type of transactions entered in a batch. The system assigns the value when you enter a transaction. Valid values are set up in user defined code table 98/IT. You cannot assign new values. All batch types are hard coded.

Related Functions

None

Related Tables

None