Craig_Potter
Reputable Poster
Re: 41/IN & integrity reports
See "A:'s" below...
Now the Q is :
1. Confirmation of the above
A: Confirmed
2. If no doc types are included in 41/IN, then system will use rule 3. In
this case for any doc type how does the system understand which DMAAI table
to look at. Will it look at all the DMAAI tables in rule3, AND wherever it
finds a matching combination of CO & GL CLASS, it will select all such
relevant object accounts, and then go on to F0911 ??
A: Sort of. It builds a list of valid Object Accounts from all the AAI's
for the rule. Then it reads the F0911 and ignores entries that are not
hitting these accounts when calculating the 'Account Ledger' value.
In that case there is always the possibility of it locating more than one
object a/c for the CO + GL Class combination.
A: Correct. When this occurs you will find entries on the R41543 report
with an Account Ledger = 0 or not easily reconciled. The workaround is to
change the 41/IN entry for that document type to a different rule. Of
course, depending on your AAI setup this workaround will not always work.
There are many SAR's around this problem both putting Doc type logic in and
then taking it out again. Most sites who experience these problems have
given up and either modified this logic or written their own integrity
programs.
2. Does it need to be set up for all user defined doc types or only for
user defined sales order/invoice, PV's i.e. Rule 1 & 2 related documents
only.
A: It only needs to be setup for those document types not suited to rule 3
(see above)
3. We would like to run the following reports on a regular basis as
scheduler jobs. Can anyone direct me if there is anything specifi!
c order in which these should be run. Given below is the order that we
propose :
- R31802 for all orders with status =95, (R31804 may be run later after
researching variances
- R09800 for posting all open batches
- R41542
- R41548
- R41544
- R41543
A: Sequence looks OK, although note that R41548 is an annual job to build
new fiscal year opening balances in the As-of file.
3. R41542 (AS OF ) will select only such records from F4111 which have the
(As of post) IPCD field as ' ' blank.
In case of work orders unless R31802 is run in final mode i.e. status is
brought to 97, the F4111 record of IM & IC will continue having a 'S' flag
for IPCD and hence will not appear in the AS OF FILE.
However, these F4111 records will obviously get considered in F41021 (ITEM
LOCATION) field for Qty on hand.
A: Correct, IPCD='S' records are not included in the As-of. The R41544
which compares the Item Location (F41021) and the Item Ledger tries to
cater for this. It includes F4111 records with a G/L Date = 0 and IPCD <>
'X', therefore your 'S' records.
Regards,
Craig
*********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager ( [email protected])
Important Notice: Berri Limited scans all incoming and outgoing
emails for possible inappropriate content. Procedures to rectify problems with the email system may result in others reviewing
the content of any incoming or outgoing email.
The Berri Limited Email system is for Business use only.
*********************************************************************
Craig Potte
See "A:'s" below...
Now the Q is :
1. Confirmation of the above
A: Confirmed
2. If no doc types are included in 41/IN, then system will use rule 3. In
this case for any doc type how does the system understand which DMAAI table
to look at. Will it look at all the DMAAI tables in rule3, AND wherever it
finds a matching combination of CO & GL CLASS, it will select all such
relevant object accounts, and then go on to F0911 ??
A: Sort of. It builds a list of valid Object Accounts from all the AAI's
for the rule. Then it reads the F0911 and ignores entries that are not
hitting these accounts when calculating the 'Account Ledger' value.
In that case there is always the possibility of it locating more than one
object a/c for the CO + GL Class combination.
A: Correct. When this occurs you will find entries on the R41543 report
with an Account Ledger = 0 or not easily reconciled. The workaround is to
change the 41/IN entry for that document type to a different rule. Of
course, depending on your AAI setup this workaround will not always work.
There are many SAR's around this problem both putting Doc type logic in and
then taking it out again. Most sites who experience these problems have
given up and either modified this logic or written their own integrity
programs.
2. Does it need to be set up for all user defined doc types or only for
user defined sales order/invoice, PV's i.e. Rule 1 & 2 related documents
only.
A: It only needs to be setup for those document types not suited to rule 3
(see above)
3. We would like to run the following reports on a regular basis as
scheduler jobs. Can anyone direct me if there is anything specifi!
c order in which these should be run. Given below is the order that we
propose :
- R31802 for all orders with status =95, (R31804 may be run later after
researching variances
- R09800 for posting all open batches
- R41542
- R41548
- R41544
- R41543
A: Sequence looks OK, although note that R41548 is an annual job to build
new fiscal year opening balances in the As-of file.
3. R41542 (AS OF ) will select only such records from F4111 which have the
(As of post) IPCD field as ' ' blank.
In case of work orders unless R31802 is run in final mode i.e. status is
brought to 97, the F4111 record of IM & IC will continue having a 'S' flag
for IPCD and hence will not appear in the AS OF FILE.
However, these F4111 records will obviously get considered in F41021 (ITEM
LOCATION) field for Qty on hand.
A: Correct, IPCD='S' records are not included in the As-of. The R41544
which compares the Item Location (F41021) and the Item Ledger tries to
cater for this. It includes F4111 records with a G/L Date = 0 and IPCD <>
'X', therefore your 'S' records.
Regards,
Craig
*********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager ( [email protected])
Important Notice: Berri Limited scans all incoming and outgoing
emails for possible inappropriate content. Procedures to rectify problems with the email system may result in others reviewing
the content of any incoming or outgoing email.
The Berri Limited Email system is for Business use only.
*********************************************************************
Craig Potte
