HI it is related to file interface ,any one please send related code to me.

Question

now am sending total object ...
1.1.     Related Business Process Information
Vendor invoices enter DISCO System electronically and then either go through the 2 -way match or 3-way match process. Since DISCO System does not handle the actual payment processing, the invoices with successful match will be ready to transfer to Enterprise SAP to generate payments.
The purpose of this interface is to detail the requirements of sending vendor open invoices to Enterprise SAP.  Payments are then processed based on the approved invoices that transfer over from DISCO.
1.2.     General Description of Functionality
All Disco approved vendor invoices will be mapped into this interfaceIFIC1001 (Interface  Vendor Invoices to Enterprise SAP) (FI001 Incoming AP Invoices to TLand). This outbound file is a flat file and the format is in TXT. The file name will be load_payable_1516.yyymmddhhmmss.txt (replacing yyyymmddhhmmss with date and time).  This is a nightly interface from DISCO to Enterprise SAP via FTP shuttle.
Business Requirements:
Enterprise SAP specific fields for interface purposes:
•     Company Code
•     Business Area
•     GL Account
•     Profit Center
•     Cost Center
•     WBS
•     MPM Issue
•     Destination Geography
•     Distribution Channel
•     COPA customer
•     Tax Code
2.     Functional Specification Details
2.1.     Detailed Functional Requirements
2.1.1.     Functional Step 1
•     Read data in table BSIK
o     If data in table then go to 2.1.3 Functional Step 3
o     If no data in table then proceed to 2.1.2 Functional Step 2
2.1.2     Functional Step 2
Notification message send to IT Support and AP Account when BSIK is empty. Then end the program.
Error Message
Empty File no FTP Transfer
2.1.3    Functional Step 3
Create Control Header record when BSIK has data.
•     The Control Header Record is the first record in the interface file. 
•     Only one Control Record is required in each file. 
•     Maximum number of 8000 lines per interface file. 
•     Several interface files will be created if there are more than 8000 lines, however, no document should ever be split between 2 files, only whole document processing.
2.1.4   Functional Step 4 
Create Pay Header
•     Use the following fields from BSIK to map the Pay Header data in the interface file.
                    Company code               BSIK-BUKRS
                    Vendor                     BSIK-LIFNR
                    Fiscal year                            BSIK-GJAHR
                    Document #               BSIK-BELNR
                    Document Date               BSIK-BLDAT
                    Currency                            BSIK-WAERS
                    Amount in LC (local currency)     BSIK-DMBTR
                    Payment Terms               BSIK-ZTERM
                    Reference                                         BSIK-XBLNR
            Debit/Credit Indicator                  BSIK-SHKZG
            Business Area               BSIK-GSBER
•     No more than 950 lines per header, if lines exceed 950 then need to create a new header, ensuring that the document is fully balanced (Debits = Credits)
o     If the value of BSIK- SHKZG = ‘H’ then
     Map ‘-’ to the subfield SIGN of the Amount_ Document _T field
     Assign ‘C’ to the subfield DRCR of the Amount_ Document _T field
o     If the value of BSIK- SHKZG = ‘S’ then
     Map ‘+’ to the subfield SIGN of the Amount_ Document _T field
     Assign ‘D’ to the subfield DRCR of the Amount_ Document _T field
o     Save the total amount of each invoice in credit and debit separately.  This data will need to map into the Control Trailer Record (see 5.5)
Create Pay Line Record
•     Read following fields from BSIK and use as input fields for table BSEG
Company code               BSIK-BUKRS
Document #               BSIK-BELNR
Fiscal year                       BSIK-GJAHR
•     When BSEG-LIFNR ≠ BSIK-LIFNR; Group details by  Document number (BSEG-BELNR), Company code (BSEG-BUKRS), Business Area (BSEG-GSBER), Profit Center (BSEG-PRCTR), Cost Center(BSEG-KOSTL), G/L Account (BSEG-HKONT), Destination Geography (BSEG-ZZDESTGEO), Distribution Channel(BSEG-ZZDIST), MPM (BSEG-ZZISSUE), and COPA Customer (ZZSOLDTO), WBS Element BSEG-PROJK***, Internal Order BSEG-AUFNR, Dr Cr Indicator BSEG- SHKZG
WBS Element logic – In BSEG-PROJK the WBS Element is stored as 8 digit #, we need to take this number and convert it to the 24 char # (PRPS_POSID), as follows:-
BSEG-PROJK = PRPS-PSPNR = PRPS-POSID
e.g.
BSEG-PROJK = 00000124
PRPS-PSPNR = 00000124 = PRPS-POSID = HE-000001.04.00001
In DISCO we are using WBS Elements starting with an Alpha char (HE = Home Entertainment, DI = DIS, AS = ASAP), and in TLand they are using all numeric id’s.
For the summarization:-
o     If the WBS element is an Alpha (i.e. DISCO) then get the cost center (PRPS-FKSTL) from the wbs element and summarize by the cost center.
o     If the WBS element is numeric (TLand) then summarize by the WBS Element.
•     The fields in BSEG are mapped in the interface as follows:
          MPM Issue                                                 BSEG-ZZISSUE
         Distribution Channel                                     BSEG-ZZDIST
         Sold To Customer (COPA Customer)        BSEG-ZZSOLDTO
          Destination Geography                               BSEG-ZZDEST
          Cost Center                                                 BSEG-KOSTL
          Profit Center                                                BSEG- PRCTR
          Business Area                                             BSEG-GSBER
          G/L Account                                                BSEG-HKONT
          Amount in Local Currency (Summarized)   BSEG-DMBTR     
          Dr/Cr indicator                      BSEG-SHKZG
o      If the value of BSEG-SHKZG = ‘S’ then
     Map ‘+‘ to the subfield SIGN of the Amount_Extended_T field
     Assign ‘D’ to the subfield DRCR of the Amount_Extended_T field
o     If the value of BSEG- SHKZG = ‘H’ then
     Map ‘-‘ to the subfield SIGN of the Amount_Extended_T field
     Assign ‘C’ to the subfield DRCR of the Amount_Extended_T field
•     Process all documents from table BSIK
2.1.5      Functional Step 5
Create the Control Trailer Record that contains the total credit, total debit, and total line processed as the last record of the interface.
2.1.6    Functional Step 6
Send acknowledgment message to IT Support and AP Accountant for successful transmission and save the interface file on the UNIX server.
Successful FTP Transfer for FI001
Remote file is load_payable_1516.yyyymmddhhss.txt
2.1.7   Functional Step 7
Clearing Transaction – this is to clear table BSIK, document by document. One transaction will be created by each Document number by Vendor. We must only clear the documents which are included in the interface.
So, in BSIK take the first document (BSIK-BELNR) and use transaction code F-44 in order to clear this document from table BSIK and transfer it to table BSAK. Process all the documents in BSIK, until BSIK is empty.
SAP Transaction code     F-44 – Clear Vendor
Screen     Clear Vendor: Header Data
Sample document(s)     
SAP system/Client for sample docs     DR1 (030)
Step 1 – using document # (BSIK_BELNR) as the key, find the following date for the selection screen
Input Field description     Map from field     Default value (if applicable)     Sample value
Account     BSIK-LIFNR          100000
Clearing date     SY_DATUM          10/06/07
Period          Default from date     1
Company Code     BSIK-BUKRS          1119
Currency     BSIK-WAERS          USD
Under ‘Additional Selection’ select the ‘radio’ button for the Document number.
Press Enter.
Step 2 – input following data
Input Field description     Map from field     Default value (if applicable)     Sample value
Document Number From     BSIK-BELNR          400000010
On menu bar select ‘Go to’ and select ‘G/L Item Fast Entry’
Step 3 – input following data
Input Field description     Map from field     Default value (if applicable)     Sample value
PK (Posting key)     BSIK-SHKZG          50
Account          APCLEARING     APCLEARING
Amount     BSIK-DMBTR          500.00
Business Area     BSIK-GSBER          135
Company Code     BSIK-BUKRS          1119
Rules for Posting Key
If BSIK-SHKZG = H then value to enter = 50
If BSIK-SHKZG = S then value to enter = 40
Then click ‘Process Open Items’
Clear any value in field DF05B-PSSKT (Cash Discnt) = make blank
Amount Entered (RF05A-BETRG) = Assigned (RF05A-NETT)
SAVE document and new ‘cleared document’ will be assigned.
Step 4 – This transaction should be repeated until all entries in the interface file are cleared.
4.1.5.     Interface File Layout mapping
The interface file contains four types of records:
•     Control Record: This is the first record on every transmission file.
o     Only one Control Record is required in each file. 
o     Maximum number of 8000 lines per interface file. 
o     Several interface files will be created if there are more than 8000 lines
•     Pay Header: This equates to BSIK-BUZEI line 001 of each document.
o     A new header line should be created whenever 950 lines of Pay Line are written
o     The records of file are broken into several headers if lines are exceeded 950.
•     Pay Line: Detailed line containing the summarized data (see 2.1.4).
•     Control Trailer: This contains totals of the whole file. Add this record at the end of file.
Message was edited by:
        Naveesh surapureddy

Answer 1

Hi,
You can use this FM to get the list of all files
TMP_GUI_DIRECTORY_LIST_FILES
  DATA: TBL_FILES LIKE SDOKPATH OCCURS 10 WITH HEADER LINE,
        TBL_DIRS LIKE SDOKPATH OCCURS 10 WITH HEADER LINE.
  CALL FUNCTION 'TMP_GUI_DIRECTORY_LIST_FILES'
       EXPORTING
            DIRECTORY  = P_DIRECTORY
            FILTER         = 'Test*.Txt'   "<< restricts to only TEXT files begining with Test
       TABLES
            FILE_TABLE = TBL_FILES
            DIR_TABLE  = TBL_DIRS.
After getting the files in the TBL_FILES... loop the table and read the files with GUI_UPLOAD FM
Thanks,
Sankar M