sitemap
| SapMaterial.com |
 | |  | |  | |  | |  | |  | |  | |  | |  |
Multiple internal-external systems-SAP-non-PO Invoices
short description
An Interface to upload non-PO invoices from external vendors and from DTE internal systems into SAP for further payments using the
Idocs.The current list of internal DTE systems is:-TMS-Electric choice-Endur-Burr Wolff-ARP All DTE internal systems will use one single flat
file format.All files should be placed in a designated server location. Files may be transferred using FTP protocol.The SAP Custom Inbound
program which is scheduled will process the files from the location and list out any errors with the files and the status of the Invoice postings
in a report (RDD-1064) on SAP which can be monitered by the users of DTE Internal systems. If any of the postings get failed the dedicated
person on the source system side should resolve the issue and re-download invoices into the file.
source application
All source systems will use one single flat file format with fixed width.All files should be placed in a server location designated for this
application using a FTP protocol from where the SAP system will be able access the files and process them.File Location for placement: Not
yet defined.Flat file with fixed width format structure: Refer to document belowIDD-1108-File-Structure-format.xls
Target Application : SAP R/3
Interface type : FTP file
Message format : IDOC
Transactions:The Custom transaction which is scheduled to process the files from the location can also be used to check the file errors
which were logged while running in background. All the file specific errors will be shown in detail. This Custom transaction will also have the
option to view the Status of posted and failed Invoices in a Report which is also available with a Transaction Code ZFNN. Check for
RDD1064 for additional details regarding the report specifications.Tables:EDIDC - Contol Record table for IdocsEDID4 - Data Record table
for IdocsEDIDS - Status record table for IdocsZDONSYS - Lookup table for Donor systemsZDON_FILE_ERR - Table to log the status of the
files.
Trigger point: batch job
Interface details:
Triggering mechanism
1.As soon as source system flat file is ready in the location , the SAP Interface program which is scheduled for every 30 minutes will map the
data from the files and create the Idocs using the Idoc Type FIDCCP01 and initiate the Inbound process in SAP.
2.SAP will process the Idoc data and post the Invoices immediately.
Data selection criteria (filtering logic)
Menu Option Button - Post Files
Default Selection Criteria for the SAP Interface program(Variant will be created to schedule in background) :
1.File Path(Only path,no file name)
2.File Name( Optional )
Menu Option Button - File Status
File Status Selection Criteria for the SAP Interface program(Will be used to check the file errors):
1. Source System - Multiple Entry
2. File Indentifier
3. Date - Range
4. Time - Range
Menu Option Button - Spool List
Opens link to report in SAP Spool directory.
Menu Option Button - Invoice List
Opens link to report for Invoice Status:Refer to RDD1064
pseudo code
Partner Profile config with following details needs to be completed either with a Logical System or the Vendor partner.
Logical System: WBISERVER
Message Type: FIDCC1
Idoc Type: FIDCCP01
Process Code: FID1
Pseudo Code for SAP Interface program:
The interface program for SAP will be scheduled to run every 30 minutes.
Start of the program
Menu Buttons: Post Files(DEFAULT), File Status, Invoice List, Spool List.
CASE: MENU BUTTON.
WHEN: Post Files.
Selection screen:(Variant in background)
FILE PATH:
FILE NAME:
Program will collect the file location path.
VALIDATE FOR FILE PATH.
IF FILE PATH NOT VALID.
WRITE THE PROCESS LOG.
EXIT.
END PROGRAM.
ELSE.
Logic:
Collect all the unprocessed files from location path.
IF UNPROCESSED FILES EXIST.
LOOP AT EACH FILE.
VALIDATE FOR FILE FORMAT AND FILE COMPLETNESS.
IF FILE INCONSISTENT.
RENAME FILE ADDING "PROC_ERR" TO THE FILE NAME.
SAVE THE FILE IN A SEPARATE LOCATION.
WRITE THE PROCESS LOG.
SAVE THE ERROR DETAIL AND FILE DETAILS IN TABLE zdon_file_err.
CONTINUE.
ENDIF.
VALIDATE FOR FILE HEADER AND TRAILER INFO.
IF FILE INCONSISTENT.
RENAME FILE ADDING "PROC_ERR" TO THE FILE NAME.
SAVE THE FILE IN A SEPARATE LOCATION.
WRITE THE PROCESS LOG.
SAVE THE ERROR DETAIL AND FILE DETAILS IN TABLE zdon_file_err.
CONTINUE.
ENDIF.
VALIDATE DATA IN FILE HEADER AND TRAILER.
IF FILE INCONSISTENT.
RENAME FILE ADDING "PROC_ERR" TO THE FILE NAME.
SAVE THE FILE IN A SEPARATE LOCATION.
WRITE THE PROCESS LOG.
SAVE THE ERROR DETAIL AND FILE DETAILS IN TABLE zdon_file_err.
CONTINUE.
ENDIF.
ADD FILE DETAILS TO ZINTERNAL TABLE.
ENDLOOP.
ENDIF.
LOOP AT ZINTERNAL TABLE.
PULL DATA FROM THE FILE TO INTERNAL TABLES.
PROCESS THE DATA IN INTERNAL TABLES TO IDOC STRUCTURE USING IDOC TYPE.
MAP DATA FROM INTERNAL TABLES TO IDOC INTERNAL TABLES.
CREATE INTERNAL TABLES OF EDIDC, EDIDD and EDIDS.
CALL FUNCTION MODULE 'INBOUND_IDOC_PROCESS'.
WRITE THE PROCESS LOG.
SAVE THE SUCCESS DETAIL AND FILE DETAILS IN TABLE zdon_file_err.
ENDLOOP.
ENDIF.
WHEN: File Status.
SELECTION SCREEN.
1.SOURCE SYSTEM(Multiple).
2.DATE RANGE.
3.TIME RANGE.
4.FILE IDENTIFIER
SELECT THE DATA FROM TABLE zdoc_file_err WITH SELECTION CRITERIA.
SHOW STATUS DETAILS IN A LIST WITH CHECK BOXES.
Options:
DELETE
IF CHECK BOXES selected and DELETE option FROM MENU FIRED.
DELETE THE RELEVANT FILE FROM THE LOCATION FOR THE CHECKED RECORDS.
DELETE THE RECORDS FROM TABLE zdoc_file_err.
ELSE.
ALERT MESSAGE "No selection checked for deletion.".
ENDIF.
WHEN: Invoice List..
CALL THE TRANSACTION ZFNN.(Refer to RDD-1064).
which will list the status of the Idocs for Invoice postings.
WHEN: Spool List..
CALL THE TRANSATION "SP01" AND PASS THE PARAMETERS REQUIRED.
LIST OF THE SPOOL WITH STATUS OF THE PROGRAM AT ALL INTERVALS WILL BE LISTED.
ENDCASE.
End of Program.
Transport mechanism
Interface error handling
Communication failures
All communication failures from source systems to the SAP File location using FTP should be handled at the source system side.
Validation failures
Validations done at the File level for File consistency will be logged and can be monitered using the Interface program which has the option
to run in foreground using a transaction code.
Validation done at File Level are for:
1. File Structure, File Header and File Trailer Data Consistency Check.
2. Completeness of the file.
3. Validation of dates and Source system in File Header.
4. Total Invoices in file to that of total Invoices given in File Trailer.
5. Total Line Items in file to that of total Line Items given in File Trailer.
6. Invoice total amount in file to that of totals of each amount in Invoices.
formatting errors.
Mentioned Above in Validation Failures
logging requirements
1.Each of the source system users should have access to the File Location to transfer the files from their location using the FTP Protocol.
2.Each of the source system users should have access to SAP Transaction to run the Interface program as well as view the report.
Notification / monitoring processess
All errors during the Idoc Inbound process and while posting the Invoices can be reviewed using a report with transaction code ZFNN (Not
finalized, NN - Number). This report can also be invoked from Interface program through a menu button
An Interface to upload non-PO invoices from external vendors and from DTE internal systems into SAP for further payments using the
Idocs.The current list of internal DTE systems is:-TMS-Electric choice-Endur-Burr Wolff-ARP All DTE internal systems will use one single flat
file format.All files should be placed in a designated server location. Files may be transferred using FTP protocol.The SAP Custom Inbound
program which is scheduled will process the files from the location and list out any errors with the files and the status of the Invoice postings
in a report (RDD-1064) on SAP which can be monitered by the users of DTE Internal systems. If any of the postings get failed the dedicated
person on the source system side should resolve the issue and re-download invoices into the file.
source application
All source systems will use one single flat file format with fixed width.All files should be placed in a server location designated for this
application using a FTP protocol from where the SAP system will be able access the files and process them.File Location for placement: Not
yet defined.Flat file with fixed width format structure: Refer to document belowIDD-1108-File-Structure-format.xls
Target Application : SAP R/3
Interface type : FTP file
Message format : IDOC
Transactions:The Custom transaction which is scheduled to process the files from the location can also be used to check the file errors
which were logged while running in background. All the file specific errors will be shown in detail. This Custom transaction will also have the
option to view the Status of posted and failed Invoices in a Report which is also available with a Transaction Code ZFNN. Check for
RDD1064 for additional details regarding the report specifications.Tables:EDIDC - Contol Record table for IdocsEDID4 - Data Record table
for IdocsEDIDS - Status record table for IdocsZDONSYS - Lookup table for Donor systemsZDON_FILE_ERR - Table to log the status of the
files.
Trigger point: batch job
Interface details:
Triggering mechanism
1.As soon as source system flat file is ready in the location , the SAP Interface program which is scheduled for every 30 minutes will map the
data from the files and create the Idocs using the Idoc Type FIDCCP01 and initiate the Inbound process in SAP.
2.SAP will process the Idoc data and post the Invoices immediately.
Data selection criteria (filtering logic)
Menu Option Button - Post Files
Default Selection Criteria for the SAP Interface program(Variant will be created to schedule in background) :
1.File Path(Only path,no file name)
2.File Name( Optional )
Menu Option Button - File Status
File Status Selection Criteria for the SAP Interface program(Will be used to check the file errors):
1. Source System - Multiple Entry
2. File Indentifier
3. Date - Range
4. Time - Range
Menu Option Button - Spool List
Opens link to report in SAP Spool directory.
Menu Option Button - Invoice List
Opens link to report for Invoice Status:Refer to RDD1064
pseudo code
Partner Profile config with following details needs to be completed either with a Logical System or the Vendor partner.
Logical System: WBISERVER
Message Type: FIDCC1
Idoc Type: FIDCCP01
Process Code: FID1
Pseudo Code for SAP Interface program:
The interface program for SAP will be scheduled to run every 30 minutes.
Start of the program
Menu Buttons: Post Files(DEFAULT), File Status, Invoice List, Spool List.
CASE: MENU BUTTON.
WHEN: Post Files.
Selection screen:(Variant in background)
FILE PATH:
FILE NAME:
Program will collect the file location path.
VALIDATE FOR FILE PATH.
IF FILE PATH NOT VALID.
WRITE THE PROCESS LOG.
EXIT.
END PROGRAM.
ELSE.
Logic:
Collect all the unprocessed files from location path.
IF UNPROCESSED FILES EXIST.
LOOP AT EACH FILE.
VALIDATE FOR FILE FORMAT AND FILE COMPLETNESS.
IF FILE INCONSISTENT.
RENAME FILE ADDING "PROC_ERR" TO THE FILE NAME.
SAVE THE FILE IN A SEPARATE LOCATION.
WRITE THE PROCESS LOG.
SAVE THE ERROR DETAIL AND FILE DETAILS IN TABLE zdon_file_err.
CONTINUE.
ENDIF.
VALIDATE FOR FILE HEADER AND TRAILER INFO.
IF FILE INCONSISTENT.
RENAME FILE ADDING "PROC_ERR" TO THE FILE NAME.
SAVE THE FILE IN A SEPARATE LOCATION.
WRITE THE PROCESS LOG.
SAVE THE ERROR DETAIL AND FILE DETAILS IN TABLE zdon_file_err.
CONTINUE.
ENDIF.
VALIDATE DATA IN FILE HEADER AND TRAILER.
IF FILE INCONSISTENT.
RENAME FILE ADDING "PROC_ERR" TO THE FILE NAME.
SAVE THE FILE IN A SEPARATE LOCATION.
WRITE THE PROCESS LOG.
SAVE THE ERROR DETAIL AND FILE DETAILS IN TABLE zdon_file_err.
CONTINUE.
ENDIF.
ADD FILE DETAILS TO ZINTERNAL TABLE.
ENDLOOP.
ENDIF.
LOOP AT ZINTERNAL TABLE.
PULL DATA FROM THE FILE TO INTERNAL TABLES.
PROCESS THE DATA IN INTERNAL TABLES TO IDOC STRUCTURE USING IDOC TYPE.
MAP DATA FROM INTERNAL TABLES TO IDOC INTERNAL TABLES.
CREATE INTERNAL TABLES OF EDIDC, EDIDD and EDIDS.
CALL FUNCTION MODULE 'INBOUND_IDOC_PROCESS'.
WRITE THE PROCESS LOG.
SAVE THE SUCCESS DETAIL AND FILE DETAILS IN TABLE zdon_file_err.
ENDLOOP.
ENDIF.
WHEN: File Status.
SELECTION SCREEN.
1.SOURCE SYSTEM(Multiple).
2.DATE RANGE.
3.TIME RANGE.
4.FILE IDENTIFIER
SELECT THE DATA FROM TABLE zdoc_file_err WITH SELECTION CRITERIA.
SHOW STATUS DETAILS IN A LIST WITH CHECK BOXES.
Options:
DELETE
IF CHECK BOXES selected and DELETE option FROM MENU FIRED.
DELETE THE RELEVANT FILE FROM THE LOCATION FOR THE CHECKED RECORDS.
DELETE THE RECORDS FROM TABLE zdoc_file_err.
ELSE.
ALERT MESSAGE "No selection checked for deletion.".
ENDIF.
WHEN: Invoice List..
CALL THE TRANSACTION ZFNN.(Refer to RDD-1064).
which will list the status of the Idocs for Invoice postings.
WHEN: Spool List..
CALL THE TRANSATION "SP01" AND PASS THE PARAMETERS REQUIRED.
LIST OF THE SPOOL WITH STATUS OF THE PROGRAM AT ALL INTERVALS WILL BE LISTED.
ENDCASE.
End of Program.
Transport mechanism
Interface error handling
Communication failures
All communication failures from source systems to the SAP File location using FTP should be handled at the source system side.
Validation failures
Validations done at the File level for File consistency will be logged and can be monitered using the Interface program which has the option
to run in foreground using a transaction code.
Validation done at File Level are for:
1. File Structure, File Header and File Trailer Data Consistency Check.
2. Completeness of the file.
3. Validation of dates and Source system in File Header.
4. Total Invoices in file to that of total Invoices given in File Trailer.
5. Total Line Items in file to that of total Line Items given in File Trailer.
6. Invoice total amount in file to that of totals of each amount in Invoices.
formatting errors.
Mentioned Above in Validation Failures
logging requirements
1.Each of the source system users should have access to the File Location to transfer the files from their location using the FTP Protocol.
2.Each of the source system users should have access to SAP Transaction to run the Interface program as well as view the report.
Notification / monitoring processess
All errors during the Idoc Inbound process and while posting the Invoices can be reviewed using a report with transaction code ZFNN (Not
finalized, NN - Number). This report can also be invoked from Interface program through a menu button
|
| ||||||||||
All of the product names here are trademarks of their respective companies. The site
www.allsaplinks.com no way affiliated with SAP AG. We have made every effort for the content
integrity. Information used on this site is at your own risk.
www.allsaplinks.com no way affiliated with SAP AG. We have made every effort for the content
integrity. Information used on this site is at your own risk.
ABAP TECHNICAL
SAP Introduction
sap abap faq
sap Tables
SAP Transaction codes
Internal tables
data dictionary
performance tuning
transports & Requests
Sap scripts
Smartforms
lsmw
reports
sap Workflow
module pool/ dialog
programming
table control
user exits
sap memory
abap memory
alv reports
ABAP ADVANCED
IDOC
ALE
BAPI
BADI
RFC
FUNCTIONAL SIDE
Materials Management
FICO
Human Resources
BIW / BW / SEM
Free Documentation
Abap Material
Ale Material
BAPI Material
BC Material
IDOC Material
R/3 Database Management
SAP material
RFC
Transport
Sales & Distribution Material
Basic Data and Function
Material
Basis (BC) Material
Billing Material
CA Material
CATT : Computer Aided Test
Tool
Capacity Evaluation and
leveling Material
Capacity Planning Material
Cross Application Material
Countries
Customer Service Material
Enterpise Material
Financial / Controlling (FICO)
Internet Time Sheet
Inspection Material
HR Material
Material Management
Material
Payments Material
Payroll Material
Pension Fund
Production Planning and
Control
Plant Maintenance
Quality Management Material
Real Estate Material
SAP material
Wage Types
SAP Introduction
sap abap faq
sap Tables
SAP Transaction codes
Internal tables
data dictionary
performance tuning
transports & Requests
Sap scripts
Smartforms
lsmw
reports
sap Workflow
module pool/ dialog
programming
table control
user exits
sap memory
abap memory
alv reports
ABAP ADVANCED
IDOC
ALE
BAPI
BADI
RFC
FUNCTIONAL SIDE
Materials Management
FICO
Human Resources
BIW / BW / SEM
Free Documentation
Abap Material
Ale Material
BAPI Material
BC Material
IDOC Material
R/3 Database Management
SAP material
RFC
Transport
Sales & Distribution Material
Basic Data and Function
Material
Basis (BC) Material
Billing Material
CA Material
CATT : Computer Aided Test
Tool
Capacity Evaluation and
leveling Material
Capacity Planning Material
Cross Application Material
Countries
Customer Service Material
Enterpise Material
Financial / Controlling (FICO)
Internet Time Sheet
Inspection Material
HR Material
Material Management
Material
Payments Material
Payroll Material
Pension Fund
Production Planning and
Control
Plant Maintenance
Quality Management Material
Real Estate Material
SAP material
Wage Types