Daily sales report VS GL Summary Report

Hi Revanth,

Good day.

If you want to achieve this target, you have to write scripts by yourself.

Part A: blueprint

1, what is daily sales?

Daily sales has to be today's sales subtract yesterday's sales.

2, what is GL summary?

Posted batches become GL summary.

Part B: structure

1, How to compare today's sales with yesterday's sales?

You need to keep a record for yesterday's sales, also a record for today's sales, both records should be different date but same time, let's say 2:00am.

those records will be a full copy of the sales records.

2, how to convert sales records to GL?

a, t_order--->(order_no)--->t_sub_lineitem--->(sli_no)--->t_sli_detail--->(pmap_no)--->t_pmap--->(gl_hold_no)--->GL.

Compare sales with GL, you have to pick up paid_amt from t_sli_detail table.

3, sales GL or Posted GL?

If you catch the script from profiler, when you post a batch, then you can create t_posting_GL_history records by yourself.

4, compare batches (batch_no in t_sub_lineitem) with post_no is  not null.

then you can match sales to GL in a cent.

5, additional benifits:

a, you can find price map setup errors, price type errors.

b, you can find transaction failure, if transaction amount is not same as paid_amt in t_sli_detail table.

c, you will have a sales detail table, you can check anything you want to know about sales.

Part C: time

Time is everything.

This exercise will take a month or more to finish.

If you have time, I can provide more infos about how to do it, otherwise, just let it be.

The canned reports will not match sales to GL, if you just do a little bit modification try to achieve this, then forget it. The simple reason is that if you can do it, Tessitura network already did it. So it has to be another way.

Answer your question,

"Any reasons why this can be caused... "

Sales reports are not linking paid_amt from pmap_no to GL, so sales reports are not GL reports.

You cannot compare apples with oranges.

have fun

Ben

Hi Revanth,

Good day.

If you want to achieve this target, you have to write scripts by yourself.

Part A: blueprint

1, what is daily sales?

Daily sales has to be today's sales subtract yesterday's sales.

2, what is GL summary?

Posted batches become GL summary.

Part B: structure

1, How to compare today's sales with yesterday's sales?

You need to keep a record for yesterday's sales, also a record for today's sales, both records should be different date but same time, let's say 2:00am.

those records will be a full copy of the sales records.

2, how to convert sales records to GL?

a, t_order--->(order_no)--->t_sub_lineitem--->(sli_no)--->t_sli_detail--->(pmap_no)--->t_pmap--->(gl_hold_no)--->GL.

Compare sales with GL, you have to pick up paid_amt from t_sli_detail table.

3, sales GL or Posted GL?

If you catch the script from profiler, when you post a batch, then you can create t_posting_GL_history records by yourself.

4, compare batches (batch_no in t_sub_lineitem) with post_no is  not null.

then you can match sales to GL in a cent.

5, additional benifits:

a, you can find price map setup errors, price type errors.

b, you can find transaction failure, if transaction amount is not same as paid_amt in t_sli_detail table.

c, you will have a sales detail table, you can check anything you want to know about sales.

Part C: time

Time is everything.

This exercise will take a month or more to finish.

If you have time, I can provide more infos about how to do it, otherwise, just let it be.

The canned reports will not match sales to GL, if you just do a little bit modification try to achieve this, then forget it. The simple reason is that if you can do it, Tessitura network already did it. So it has to be another way.

Answer your question,

"Any reasons why this can be caused... "

Sales reports are not linking paid_amt from pmap_no to GL, so sales reports are not GL reports.

You cannot compare apples with oranges.

have fun

Ben