1.

What Condition Should Exist For Store Based On Which Saexpgl Batch Picks Up The Data To "stg_fif_gl_data" Table?

Answer»

SAEXPGL exports totals to ORACLE FINANCIAL Application general ledger for: 

  • Sales transactions 
  • Tenders 
  • Paid-ins 
  • Paid-outs 
  • Taxes 

This export batch module works by first GETTING the store day. Then it finds the totals to export and verifies that individual totals CONTAIN no errors for either the store/day (if store/day is the unit-of-work defined by the user) or store/day/total (if store/day/total is the unit-of-work defined by the user). Next the module looks at the SA_FIF_ORA_CROSS_REF table to determine which Oracle account ID (Cost Center ID) it needs to export to. Determine if the selected store/day/total has been previously exported; if so, reverse the previous posting, and post the latest adjustments to the General Ledger (GL) staging table. Finally it moves the data to the Oracle staging GL_INTERFACE. (No RMS staging table is involved.)

SAEXPGL exports totals to Oracle Financial Application general ledger for: 

This export batch module works by first getting the store day. Then it finds the totals to export and verifies that individual totals contain no errors for either the store/day (if store/day is the unit-of-work defined by the user) or store/day/total (if store/day/total is the unit-of-work defined by the user). Next the module looks at the SA_FIF_ORA_CROSS_REF table to determine which Oracle account ID (Cost Center ID) it needs to export to. Determine if the selected store/day/total has been previously exported; if so, reverse the previous posting, and post the latest adjustments to the General Ledger (GL) staging table. Finally it moves the data to the Oracle staging GL_INTERFACE. (No RMS staging table is involved.)



Discussion

No Comment Found