Convert tally data to SAP B1

Is it possible to transfer 1 year tally data through DTW into SAP B1, what configuration will i required in DTW Business Object template.

Hi
i,
There are lot of documents available in this link use s-user id & password to access it.
https://websmp203.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000680297&_SCENARIO=01100035870000000183&_ADDINC=011000358700002837782005E&
You need to arange the Data From Tally To XL as SAP Bone Wants, So See The Tempates Located in
C:\Program Files\SAP\SAP Business One\AddOns\sap\DTW\DTW Templates
Mohamed Zubair

Similar Messages

Tally data to SAP B1

Respected Sir,
Anyone can tell me how we convert tally data into SAP B1?
actually one of my client using tally for finance. Rightnow that client is ready to impliment sapb1 erp package. But he wants to convert 5 year data of tally into SAP B1. Sp tell how it is possible to import that data from tally to sapb1. Please suggest me As soon as possible.
with regards,
Ambesh tripathi..

Hi Ambesh,
Have you asked the porspect(Customer) Why do he need 5 Years data in new SAP system?
If the sole purpose is only to have access to old information, then it is advisable to keep old system available in one PC.
I suggest to bring only master data and opening balance information from old/legacy system, you may use DTW for this task.
Otherwise I don't think you will be able to transfer all the data through DTW.Because Tally do not have concept of Codes for master information like Busine ss Partenr Code / Item Code / GL Code / Tax Codes / Ware Houses etc. So you will have to first create BP Master,Item Maser,Chart Of Account etc. master data and then you will be require to attach all this newly defined codes in every exported transaction of Tally. This is just to give you estimate of complexity and volume of work you are looking for.
BR
Samir Gandhi

Function module for convert date as sap internal format ?

Hi All,
Is there any standard function module to convert the date filed as SAP internal date?
My problem is while uploading data from excel sheet date filed can be any format
for exp: dd/mm/yyyy or mm/dd/yyyy or yyyy/dd/mm or dd-mm-yyyy,mm-dd-yyyy
             dd-mm-yyyy or dd.mm.yyyy or mm.dd.yyyy etc...
In our case there is no particular format in excel it can be differ for each user. I know we have few FM's in standard.
But those are not working for my req. pls help me if you have any idea.
Thanks in advance.
Regards,
Venkat Mote.

Hi Venkatesh,
Can you please check with the following function module. For my case, it is working fine.
CALL FUNCTION 'CONVERT_DATE_TO_INTERN_FORMAT'
EXPORTING
    datum = p_gs_date
    dtype = 'DATS'
IMPORTING
    idate = p_gs_date
Hope it helps to you.
Regards
Rajkumar Narasimman

How to convert the flat file data into sap tables . ?

how to upload flat file data into sap table . before upload mapping is also there in some filds . any one can give me some steps how to upload and mapping . ?

Hi
See the sample code
REPORT zmmupload.
Internal Table for Upload Data
DATA: i_mara like MARA occurs 0 with header line
PARAMETERS: p_file LIKE ibipparms-path. " Filename
At selection-screen on Value Request for file Name
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file.
Get the F4 Values for the File
CALL FUNCTION 'F4_FILENAME'
    EXPORTING
      program_name = syst-cprog
      dynpro_number = syst-dynnr
    IMPORTING
      file_name     = p_file.
Upload the File into internal Table
CALL FUNCTION 'UPLOAD'
    EXPORTING
      filename                = p_file
      filetype                = 'DAT'
    TABLES
      data_tab                = i_mara
    EXCEPTIONS
      conversion_error        = 1
      invalid_table_width     = 2
      invalid_type            = 3
      no_batch                = 4
      unknown_error           = 5
      gui_refuse_filetransfer = 6
      OTHERS                  = 7.
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
Upload the Data from Internal Table
MODIFY MARA from TABLE i_MARA.
Regards
Anji.

DIFFERENCE BETWEEN TALLY ERP AND SAP BUSINESS ONE

Hello Experts,
From where i can find the comparison between TAlly ERP and SAP business one ?

Tally 9.0
Accounting
. To fulfill legal requirements - records as per standards and practices
. To pay taxes to various bodies - statutory needs
. Keep the business running - manage receivables & payables, cash, bank...
. Keep a watch on the pulse of the organisation - key performance indicators
. Respond to queries - to locate the right transaction immediately
. With the entry of a voucher (this is what we call all accounting transactions) all books of accounts, all reports, all totals & sub-totals are updated instantly. There is nothing more that needs to be done - whether you are inserting a forgotten entry, or correcting one.
. Taxation requirements of all the states of India are available, in the prescribed formats.
. Supporting tasks like reminder letters, delayed interest, ageing, bank reconciliation.
. One single dashboard to look at all important business ratios.
. Drill down from any report, even the Balance Sheet, right to any voucher or filter and search.
. Data entry in the language of the users choice - and report in any other language (from the languages supported).
. Mark vouchers that are draft as 'optional' and convert these to final- with one button click
Financial Management & Controls
Tally.ERP 9 comes with rich features & financial reports that give you the necessary management and control of your business. A few of these are listed below:
u2022 Funds Flow & Cash Flow reports - help you locate bottlenecks
u2022 Bank reconciliation - keeps your bank books in sync, and identify unclear instruments
u2022 Customer Credit Limits - to limit risk of default and large losses
u2022 Budgets - keep tabs on projected expenses against actuals
u2022 Mark vouchers post dated - these will reflect into the books of accounts only on/after that date
u2022 For needs where reports have to consider a transaction that has not happened (say salaries for this month that get paid the next month) vouchers (called 'reversing journals') can be marked to 'disappear' for reports post a specific date
u2022 "Scenario" management - helps you with your business forecasting and planning. You can use optional, reversing journals and memorandum vouchers, to aid in recording provisional entries that are useful for interim reports
u2022 Multiple inventory valuation. You can decide one valuation method for the business, and be able generate financial reports using any other valuation method - as the  statutory method may not be appropriate for your needs, your bankers and for other decisions
u2022 Cash balances can go negative - you can get warned if this is about to happen, or see reports and make the necessary corrections
u2022 Several business exceptions are available (negative stocks, negative ledgers) - for
you to exercise control over these activities
u2022 A one-screen business ratios with drill down right up to the transactions - help you to correct course frequently u2022 Item wise & document wise profitability statements to control revenue leakage and inappropriate pricing
u2022 Internal audits are supported with audit controls - authorised users can mark vouchers as 'audited' and can get to see reports on changes made post audit, and the name of the person making the change
Inventory Accounting & Management
If you deal in goods, of any type, you'll appreciate the Inventory capabilities in Tally.ERP 9.
You can comprehensively record all types of inventory transactions, using goods receipt notes, delivery notes, stock journals, manufacturing journals and physical stock journals. All stock movements are fully recorded and maintained in stock registers.
Developed for all manufacturers, distributors, wholesalers or traders a small list of features are briefly described below:
Manufacturers:
. Bill of materials and Manufacturing Journals, to record material conversions
. Compound bill of materials support, for units that contain assemblies
. Multiple locations (godowns)
. Excise for manufacturers, including all documentation and invoice
. Costing for jobs
Distributors & Wholesalers:
. Multiple price lists, with effective dates of applicability
. Use multiple units of measure (say KG's & grams)
. Dual units of measure (say KG's and bags, to support variations as happens in commodities)
Traders:
. High speed billing, with support for POS printers
. Bar code support
. Automatic application of taxes
. Service billing & service tax
. Integrated sales return in bills
. Print bills (and any other document) in the customers language
Common:
. You can choose to de-link the computed inventory value to automatically appear in
   your financial statements - and enter this figure manually.
. Stock ageing reports, to identify slow and non-moving stocks
. Invoice profitability reports to keep a pulse on sales
. Multi-currency transactions - buy and sell across the world - with integrated forex  gain/loss calculations
. Physical stock take records to adjust physical vs. actual stocks
. Maintain batch & expiry details
Purchases & Payables: from Order to Payment
Tally.ERP 9 delivers the entire purchase cycle whether the need is the complete purchase order - goods receipt - rejections & returns - advances, debits & payments or a single payment entry, fulfilling all needs.
To ensure that you have the right stocks and minimize carrying costs, Tally.ERP 9 delivers the following to improve purchase orders:
. Define Re-order levels as a definite number or based on consumption
. Define minimum quantity to order as a definite number or based on consumption
. Pull up a report that shows the stock position, including complete details of open purchaseorders, sales orders that need to be fulfilled - check on past purchase history, and then place orders
. Optionally stagger delivery dates in the PO
When receiving goods:
. Make entries in accordance with supporting documentation, including errors your suppliers could have made (say of multiplication & round off)
. Incorporate additional costs
. Automatically manage input taxes
. Flexibility allows receipt of goods, quantities and rates different from that ordered - since this is common in real life
. Record samples & free items (using different 'actual' & 'billed' quantities)
. Multiple receipts for one order or one receipt for multiple orders, or against verbal ordersIn case there is a need to add other costs (say coolie and cartage) these additional charges can be apportioned to the cost of goods purchased.
Supplied goods may not match your needs and these are managed by the 'Rejections Out' inventory voucher. Supplier dues, input taxes and inventory positions are updated.
Suppliers often indicate likely profits, which may not be met. In case such assurances are made, you can look at Item profitability reports, and get the facts right. You could then negotiate a rebate and record this as a debit note.
Keep tabs of how much is due to whom, when. Manage advances, payables & post dated checks. Ensure there are no errors in payments - print checks from Tally.ERP 9.
Sales & Receivables: from Order to Receipt
The lifeline of a business, efficiencies in sales operations, both of goods & services, directly impact growth and profitability. The need to optimise and keep a close watch here requires exceptional capabilities from your business IT system - and Tally.ERP 9 meets these demands.
The sales process is supported with the following documents:
. Quotations - records of quotes
. Sales orders - accepted customer orders
. Deliver Notes - documents that accompany goods
. Sales Invoices/Cash Bill - to record the sale
. Credit Notes - for financial adjustments
. Rejections in - for goods returns
. Receipts - for advances and receipts
Do you have cash sales (sales across the counter)? With support for Point of Sale printers, bar codes and receipts in multiple tenders, you POS enable your business at no additional cost. Product sales may come with added services - and the integrated product & service billing will close this.
Enforce credit limits, where needed. Along with the Payment Performance of Debtors report you can identify persistent problems and take necessary business decisions. Interest for delays & reminder letters aid in collection.
For businesses engaged in Excisable goods, you get full support for Excise for Traders & Manufacturing Excise - matter of fact a business could be both!
Make multiple deliveries from one order, or one from multiple orders - this common need is available across all documents of the sales process.
Do you have multiple classes of customers? You can easily setup multiple prices (even in advance and specify the date from which they are effective).
Discounts against the line, or for the document, additional charges as a percentage or lump sum, automatic round off of bill totals, automatic computation of VAT & Service tax, returns & exchanges are all available.Need to verify that you are making the desired sales margins? Item wise and bill wise profitability reports will help you keep tabs.
Multi-company
Security: With multiple companies, possibly including personal accounts, you may need to control who gets access to which companies, and to do what. You can set up users, grant or deny access - and these are defined for each company.
Remote Access: You choose to specify which company is accessible remotely. You choose which remote users have access; you decide what access a remote user gets.
Central User Management: Users come and go. You might also have a password policy requiring users to change passwords every few weeks. You can take advantage of the ease of central user and password management that Tally.NET identities carry - and even remotely manage these while not in office.
Special NeedsMulti-CompanyMulti-PeriodMulti-Cost/Profit CentresMulti-CurrencyMulti-UnitsMulti-Location InventorySecurity and Access Control Remote Access
What is Series B
This Series will deliver major enhancements both in entirely new areas of functionality as well as in technology capabilities.
Technology & Capability Enhancements
Multi-session
Support for multiple application windows, which can even be launched by clicking on a mail link or a 'shortcut., Each of these are simultaneous 'windows' into different areas of your business processes & reports. Dynamic data refresh and the display of different views when resizing - for e.g. smaller windows displaying a more consolidated view of data, will improve organizational management and productivity.
Multi-threaded
A 'thread' is a specific task that is being performed by the microprocessor. Enhanced capabilities will be enabled such that each application window can perform more tasks simultaneously instead of linearly, including processing messages from the server. Multi-core processors, even on the desktop, are now common. We will take full advantage of these as well.
Multi Stack Architecture for Scale-up & Scale-down Deployments
To deliver the capabilities described above, and the ones that follow, Tally.ERP 9 will become 'componentised' - consisting of several layers of programs - often referred to as 'n-tier architecture'.
These software components are horizontally scalable, meaning that you can add one more computer to increase the computing power needed for a layer. In the same way, you can remove systems as needed, or collapse them into a single system - all of them even on a notebook, if required.
High Transaction Capacity with Low Latency & Management
Let us say that you start generating a report that needs to be extracted from a few thousand vouchers. This process is run in a 'session', which is isolated from all other users. Even if other users delete or modify any of the vouchers needed for the report while the report is being compiled, there is no impact on this session and you will get to see the report as if these other users did not exist.
In the same way, the user performing the edit will also be isolated. After the edit, he can open the voucher and see it with the changes he made, perhaps even delete it.
The architecture described above will in itself deliver substantial performance and transaction handling capacity. To push performance further in those cases when the storage media (typically the hard disk) is busy with other operations, additional capabilities will store these transactions 'temporarily' in a 'Q' for later write, while the user is free to continue his work (these transactions are protected against power failures and so on).
Payment Engine for Debit & Credit Cards
The facility for online payments using a variety of payment mechanisms (NEFT, online banking, credit cards), as well as receive payments (Debit / Credit Cards, NEFT etc) will be available.
Functional Enhancements
Online Banking and Reconciliation
Collaborating with Banks who wish to facilitate their customers with this capability, we will provide Online Banking - including Payment Instructions, Standing Instructions, DD, NEFT,RTGS Transfers, Balance Queries, Instruction Status, Automated or Semi-Automated Bank Reconciliation.
Point-of-Sale for most Retail Environments
Series B will support dedicated POS terminals, with Credit/Debit Card, Discount Coupons and various other payment mixes, Loyalty support, schemes, multi-layered supervisory control, simultaneous keyboard and scanner controls, integrated or isolated printing of bill and credit card authorisation slips, item substitution, rate markup/markdowns, integration with measuring devices - such as weighing scales, bill suspension and retrieval, bill reversals and cancellations, etc. It can also be used for other store operations (receipting, inventory management etc), and general business operations (finance and accounts) - both on the same machine or separate machines.
Income Tax
Comprehensive IT coverage encompassing corporate & individual income tax, including typical payroll requirements and e-Returns will be available.
EXIM Documentation
Import & export documentation has become a growing need with the world economy becoming more open. This requirement will be supported, additionally covering the processes that need to be managed along with the documentation.
Job Costing
The enhanced Job Costing functionality will support most job costing needs to a level of granularity that is increasingly needed. We expect that you will be able to handle most, if not all, project accounting needs as well.
Fixed Assets
To take advantage of tax breaks as well as to manage organizational assets, this feature will support all requirements - from opening assets, adding, removing, amalgamating, grouping, vendor tagging, AMC's, servicing, service calendars, repairs and upkeep, refurbishing, breaking-down, depreciating and disposal for complete fixed asset management.
Tally Addons Manufacturing Excise software, Tally Report Writer, Material Requirement Planning, Audit TrailVoucher-Type Level Security, SMS Plugin for Tally

How to get purchasing data from SAP R/3 to OWB (Oracle warehouse builder).

Hi,
My name is Pavan Tata. I work as a SAP BW developer. Here is the situation at my client place. Client decided to retire BW system and wants to replace with OWB(Oracle warehouse). In all this currently we have purhchasing application in BW production system and wants to move this application to OWB for the same type of reporting what they are getting currently.
Here is my question:
How to get purchasing data from SAP R/3 to OWB(Warehouse) with initial full loads and deltas mechanism in the same way as we do in BW.
Please help on this, also send me any documentation about this if you have.
Thanks,
Pavan.

Hello,
here is a short report which converts S012 entries to strings with separator semicolon. Perhaps this will help you?
Regards
Walter Habich
REPORT habitest2 LINE-SIZE 255.
TYPES:
strtab_t TYPE TABLE OF string.
CONSTANTS:
separator VALUE ';'.
DATA:
it_s012 LIKE s012 OCCURS 0,
wa_s012 LIKE s012,
strtab TYPE strtab_t,
strele TYPE string.
SELECT * FROM s012 INTO TABLE it_s012 UP TO 100 ROWS.
PERFORM data_to_string
TABLES
    strtab
USING
    'S012'. "requires it_s012 and wa_s012
LOOP AT strtab INTO strele.
WRITE: / strele.
ENDLOOP.
*&      Form data_to_string
FORM data_to_string TABLES strtab TYPE strtab_t
                    USING ittab TYPE any.
DATA:
    h_zaehler TYPE i,
    line_str TYPE string,
    l_tabellenname(10) TYPE c,
    l_arbeitsbereichsname(10) TYPE c,
    h_string TYPE string,
    h_char(255) TYPE c.
FIELD-SYMBOLS: <l_tabelle> TYPE ANY TABLE,
                 <l_arbeits> TYPE ANY,
                 <feldzeiger> TYPE ANY.
CLEAR strtab.
CONCATENATE 'IT_' ittab INTO l_tabellenname.
ASSIGN (l_tabellenname) TO <l_tabelle>.
CONCATENATE 'WA_' ittab INTO l_arbeitsbereichsname.
ASSIGN (l_arbeitsbereichsname) TO <l_arbeits>.
LOOP AT <l_tabelle> INTO <l_arbeits>.
    CLEAR: h_zaehler, line_str.
    line_str = ittab.
    DO.
      ADD 1 TO h_zaehler.
      ASSIGN COMPONENT h_zaehler OF
        STRUCTURE <l_arbeits> TO <feldzeiger>.
      IF sy-subrc <> 0. EXIT. ENDIF.
      WRITE <feldzeiger> TO h_char LEFT-JUSTIFIED.          "#EC *
      h_string = h_char.
      CONCATENATE line_str separator h_string INTO line_str.
    ENDDO.
    APPEND line_str TO strtab.
ENDLOOP.
ENDFORM.                    "data_to_string

How can i convert the date from M to MM ?

Dear Guru ,
I need to upload my list to SAP table , and in the list , we are using YYYY/M/D format ( Eg. 2010/5/20 , 2010/10/1 ) .
And now i want to convert all date format to YYYY/MM/DD , Is it possibile to do that ?
Here is my code , but it doesn't work . It returned "2009//3//5" format .
data: ld_date_int type datum.
data : test(10) type c.
test = '2009/3/5' .
ld_date_int = test .
WRITE : SY-SUBRC , LD_DATE_int .
Does SAP provide a standard function can convert the date format ?
Thanks .
Best Regards,
Carlos Zhang

Hi Dear
You can try in this way :::
data: ld_date_int type string.
DATA : ld_string TYPE string.
data : test(10) type c,
       ld_res1(4) TYPE c,
       ld_res2(2) TYPE c,
       ld_res3(2) TYPE c.
DATA : ll_res2 TYPE i,
       ll_res3 TYPE i.
test = '2009/03/5' .
ld_date_int = test .
ld_string = strlen( ld_date_int ).
CASE ld_string.
WHEN 10.
   WRITE : SY-SUBRC , LD_DATE_int.
WHEN OTHERS.
    SPLIT ld_date_int at '/' INTO ld_res1 ld_res2 ld_res3 in CHARACTER MODE.
    ll_res2 = strlen( ld_res2 ).
    ll_res3 = strlen( ld_res3 ).
    IF NOT ll_res2 eq 2 and not ll_res3 eq 2.
      CONCATENATE: '0' ld_res2 INTO ld_res2.
      CONCATENATE: '0' ld_res3 INTO ld_res3.
      CONCATENATE ld_res1 '/' ld_res2 '/' ld_res3 INTO ld_date_int.
      WRITE : SY-SUBRC , LD_DATE_int.
    ENDIF.
    IF ll_res2 eq 2 and not ll_res3 eq 2.
      CONCATENATE '0' ld_res3 INTO ld_res3.
      CONCATENATE ld_res1 '/' ld_res2 '/' ld_res3 INTO ld_date_int.
      WRITE : SY-SUBRC , LD_DATE_int.
    ENDIF.
    IF NOT ll_res2 eq 2 and ll_res3 eq 2.
       CONCATENATE: '0' ld_res2 INTO ld_res2.
        CONCATENATE ld_res1 '/' ld_res2 '/' ld_res3 INTO ld_date_int.
         WRITE : SY-SUBRC , LD_DATE_int.
    ENDIF.
ENDCASE.

How can I convert a file in SAP RDI format?

HI All,
I have to convert the data which is to be passed to the Smartform into RDI format.
I am using Application form (Print Workbench)
for sending data to smartform.
Is there any Function Module for converting data into SAP RDI format?
Should I write this FM in User-exit of application form?
Thanks & Regards,
Anshumita.

HI
GOOD
I NEVER FACED SUCH KIND OF ISSUES, BUT HERE I AM GIVING SOME DETAILS ABOUT SAP RDI FORMAT,I HOPE THIS WILL HELP YOU TO SOLVE YOUR PROBLEM.
Description
Using the SAPscript Raw Data Interface (RDI), you can connect external text management systems to control individual requests, for example, optimizing postage expense. The interface contains all form data from the R/3 System, but no layout information such as font or page size. The external system alone is responsible for the layout and administration of the document data. The RDI is of special importance for mail processing. The external system sorts the document data from the interface and forwards the documents accordingly.
The Raw Data Interface is a certified interface and allows easy connection to external systems. However, you pay the price for this extra function, as you lose tight integration with the R/3 System. For example, you cannot find out from within an R/3 application whether the external system successfully printed and sent the documents. In addition, extra expense is incurred each time you adapt a standard form, since the system has to adapt both an internal and external form. The external tool is not an integral part of the ABAP Development Workbench, so that field information (field type, output length and so on) from the ABAP Dictionary is not available.
THANKS
MRUTYUN

How to derive month/year from date in SAP BW 3.5 data flow

Hi
How we can derive cal year/month and fiscal month/year from date in SAP BW 3.5 data flow (we're using transfer and update rule)..
Thanks,
PK

Hi,
if you have any date filed in source side you can just map to any time char system will automatically convert to target objects.
please look at the screen shot for understanding. (not 3.x it is 7.x)
Thanks,
Phani.

How can i convert the data from mutiple-table to the other database(MSSQL)?

Dears,
How can i convert the data from mutiple-table to the other database such as MS-SQL?
I have a third party system based on MS-SQL 2000.
Now we want to make a integration between SAP R/3(Oracle) and SQL server.
When my user releases the purchase order in R/3, the application we coded will convert the releated data to the temp database on the SQL server.
But i don't know which tools will help me reach the purpose. BAPI, LSMW, IDoc... ???
Would anybody tell me which way is better and how to do?
Thanks a lot!
Kevin Wang

Hello Kevin,
The question to use which method depend on your detail requirements. If you use BAPI, you need to find which Bapi can provide the data you want. Bapi normally use as a function called by external system. So you need to develop an external program like VB/Java to call this Bapi and move it to SQL. LSMW is use when you want to upload data from an external system to SAP. So it does not serve your requirement. Idoc can be use to export data to an external system. Again like Bapi, you need to find what Idoc can provide the data you want. However, it does not any programming from the external system. If I were you, based on your requirements, I think writing an Abap program that read the data you want and download it to NT/SQL server will be faster and easier.

XML data into sap

Hi guys,
How to upload a XML file into sap?
is there any function module?
can anybody give me an example program for converting or uploading XML data into sap.
regards,
vinoth.

Hi all,
The XML code and XML file given is running fine for me, but when i am using it, my XML file and code, the tables GV_header and GT_item are filling in the perform but outside perform it's empty. Please find the code and XML file , PLease give the answer its urgent, points will be given for sure.
My function module code is:-
FUNCTION Z_MMI_XML_EXTRACT_COPY.
""Local interface:
*"       IMPORTING
*"             REFERENCE(DOCTYPE) LIKE DRAW-DOKAR
*"             REFERENCE(DOCNUM) LIKE DRAW-DOKNR
*"             REFERENCE(DOCVER) LIKE DRAW-DOKVR
*"             REFERENCE(DOCPART) LIKE DRAW-DOKTL
*"       TABLES
*"              T_HEADER STRUCTURE ZFI_HEADER
*"              T_ITEMS STRUCTURE ZFI_ITEMS
Load iXML Lib.
type-pools: ixml.
class cl_ixml definition load.
data: G_IXML type ref to if_ixml.
data: STREAMFACTORY type ref to if_ixml_stream_factory.
data: ISTREAM type ref to if_ixml_istream.
data: DOCUMENT type ref to if_ixml_document.
data: PARSER type ref to if_ixml_parser.
You should provide the parameter for file name
*LV_FILE_URL = 'C:input_xml.xml'.
types: begin of XML_LINE,
        DATA(256) type x,
      end of XML_LINE.
***types: begin of TY_HEADER,
        CUST_NAME(20)     type c,
        CARD_NO(20)       type c,
        TAX_AMOUNT(10)    type c,
        TOTAL_AMOUNT(10) type c,
      end of TY_HEADER.
***types: begin of TY_ITEM,
        ITEM_NO(4)      type n,
        ITEM_ID(20)     type c,
        ITEM_TITLE(50) type c,
        ITEM_QTY(10)    type c,
        ITEM_UPRICE(10) type c,
      end of TY_ITEM.
*data: GV_HEADER type TY_HEADER.
*data: GV_HEADER like zfi_header occurs 0 with header line.
data : GV_HEADER LIKE ZFI_HEADER.
*data: GT_ITEM   type standard table of TY_ITEM   with header line.
*data: GT_ITEM type standard table of zfi_items with header line.
data: GT_ITEM type standard table of zfi_items with header line.
data: XML_TABLE      type table of XML_LINE,
      XML_TABLE_SIZE type i.
data: LV_FILE_URL type rlgrap-filename.
DATA : BEGIN OF itab OCCURS 0,
a(100) TYPE c,
END OF itab.
DATA: xml_out TYPE string .
DATA : BEGIN OF upl OCCURS 0,
f(255) TYPE c,
END OF upl.
DATA: xmlupl TYPE string .
DATA : BEGIN OF wa_draw OCCURS 0,
         dokar LIKE draw-dokar,
         doknr LIKE draw-doknr,
         dokvr LIKE draw-dokvr,
         doktl LIKE draw-doktl,
         END OF wa_draw.
DATA : g_documenttype LIKE bapi_doc_aux-doctype,
         g_documentnumber LIKE bapi_doc_aux-docnumber,
         g_documentpart LIKE bapi_doc_aux-docpart,
         g_documentversion LIKE bapi_doc_aux-docversion.
*" Itab required in IMPORTING parameter of BAPI
DATA : t_documentfile LIKE bapi_doc_files2 OCCURS 0 WITH HEADER LINE.
DATA : t_documentstructure LIKE bapi_doc_structure OCCURS 0 WITH HEADER
LINE,
itab required in TABLES parameters of BAPI
       t_documentfiles LIKE bapi_doc_files2 OCCURS 0 WITH HEADER LINE,
       t_components LIKE bapi_doc_comp OCCURS 0 WITH HEADER LINE,
       t_return LIKE bapiret2.
DATA : l_docfile TYPE string.
***FILL THE TYPE OF ATTACHMENT in IMPORTING itab**
t_documentfile-wsapplication = 'XML'.
APPEND t_documentfile.
wa_draw-dokar = DOCTYPE.
wa_draw-doknr = DOCNUM.
wa_draw-doktl = DOCPART.
wa_draw-dokvr = DOCVER.
CALL FUNCTION 'BAPI_DOCUMENT_CHECKOUTVIEW2'
    EXPORTING
      documenttype              = wa_draw-dokar
      documentnumber            = wa_draw-doknr
      documentpart              = wa_draw-doktl
      documentversion           = wa_draw-dokvr
      documentfile              = t_documentfile "IMPORTING itab of BAPI
     getstructure              = '1'
     getcomponents             = 'X'
ORIGINALPATH              = ' '
HOSTNAME                  = ' '
     getheader                 = 'X'
DOCBOMCHANGENUMBER        =
DOCBOMVALIDFROM           =
DOCBOMREVISIONLEVEL       =
   IMPORTING
     return                    = t_return
   TABLES
     documentstructure         = t_documentstructure
     documentfiles             = t_documentfiles "TABLES itab of BAPI
     components                = t_components
LOOP AT t_documentfiles .
ENDLOOP.
l_docfile = t_documentfiles-docfile.
The next step is creating the main factory for the iXML library:
G_IXML = cl_ixml=>create( ).
Now Create Stream Factory
STREAMFACTORY = G_IXML->create_stream_factory( ).
CALL FUNCTION 'GUI_UPLOAD'
EXPORTING
*filename = 'C:DMS_SPA.XML'
filename = l_docfile
filetype = 'BIN'
IMPORTING
   FILELENGTH = XML_TABLE_SIZE
TABLES
data_tab = XML_TABLE.
ISTREAM = STREAMFACTORY->create_istream_itable( table = XML_TABLE
                                                size = XML_TABLE_SIZE )
Create XML Document instance
DOCUMENT = G_IXML->create_document( ).
Create parser Object
PARSER = G_IXML->create_parser( stream_factory = STREAMFACTORY
                                ISTREAM = istream
                                DOCUMENT = document ).
Parse an XML document into a DOM tree
*parser->parse( ).
Parsing Error Processing
if PARSER->parse( ) ne 0.
if PARSER->num_errors( ) ne 0.
    data: PARSEERROR type ref to if_ixml_parse_error,
          STR        type STRING,
          I          type i,
          COUNT      type I,
          INDEX      type i.
    COUNT = PARSER->num_errors( ).
    write: COUNT, ' parse errors have occured:'.
    INDEX = 0.
    while INDEX < COUNT.
      PARSEERROR = PARSER->get_error( INDEX = index ).
      I = PARSEERROR->get_line( ).
      write: 'line: ', i.
      I = PARSEERROR->get_column( ).
      write: 'column: ', i.
      STR = PARSEERROR->get_reason( ).
      write: STR.
      INDEX = index + 1.
    endwhile.
endif.
endif.
Close the stream since it ï¿½s not needed anymore
call method ISTREAM->close( ).
clear ISTREAM.
DATA : GV_NODE type ref to if_ixml_node.
DATA : GV_NODETEXT type STRING.
data: GV_FIRST_TIME.
GV_FIRST_TIME = 'X'.
GV_NODE = DOCUMENT.
*GT_ITEM-item_no = 1.
GT_ITEM-itemno_acc = 1.
perform GET_DATA tables     GT_ITEM
                 using      GV_NODE
                 changing   GV_HEADER.
Last item is still not added.
append GT_ITEM.
APPEND GV_HEADER.
*T_HEADER[] = gv_header[].
t_items[] = gt_item[].
**write : GV_HEADER-cust_name,
        GV_HEADER-card_no,
        GV_HEADER-tax_amount,
        GV_HEADER-total_amount.
**loop at GT_ITEM.
write /:.
write : GT_ITEM-item_no,
          GT_ITEM-item_id,
          GT_ITEM-item_title,
          GT_ITEM-item_qty,
          GT_ITEM-item_uprice.
**endloop.
ENDFUNCTION.
      FORM Get_data                                                 *
***form get_data tables   YT_ITEM    structure gt_ITEM
             using value(x_node) type ref to if_ixml_node
             changing Y_HEADER   type TY_HEADER.
form get_data1 tables   YT_ITEM    structure zfi_items
              using value(x_node) type ref to if_ixml_node
              changing Y_HEADER   type zfi_header.
***form get_data tables   YT_ITEM    structure GT_ITEM
             using value(x_node) type ref to if_ixml_node
             changing Y_HEADER   type TY_HEADER.
data: INDENT      type i.
data: PTEXT       type ref to if_ixml_text.
data: STRING      type string.
data: TEMP_STRING(100).
case X_NODE->get_type( ).
    when if_ixml_node=>co_node_element.
      STRING = X_NODE->get_name( ).
      GV_NODETEXT = STRING.
    when if_ixml_node=>co_node_text.
      PTEXT ?= X_NODE->query_interface( IXML_IID_TEXT ).
      if PTEXT->ws_only( ) is initial.
        STRING = X_NODE->get_value( ).
        case GV_NODETEXT.
         when 'Customer'.
            when 'HEADER'.
            clear GV_HEADER.
         when 'Name'.
           when 'INVOICE_IND'.
           move STRING to GV_HEADER-cust_name.
            move STRING to GV_HEADER-INVOICE_IND.
          when 'CompanyCode'.
            move STRING to GV_HEADER-CompanyCode.
          when 'OBJ_TYPE'.
            move STRING to GV_HEADER-OBJ_TYPE.
          when 'username'.
            move STRING to GV_HEADER-username.
          when 'PO_reference'.
            move STRING to GV_HEADER-PO_reference.
          when 'Invoice_Date'.
            move STRING to GV_HEADER-Invoice_Date.
          when 'Posting_Date'.
            move STRING to GV_HEADER-Posting_Date.
          when 'Amount'.
            move STRING to GV_HEADER-Amount.
          when 'Currency'.
            move STRING to GV_HEADER-Currency.
*APPEND GV_HEADER.
        Iteam details
          when 'invoice_doc_item'.
            move STRING to GT_ITEM-ITEMNO_ACC.
          when 'currency'.
            move STRING to TEMP_STRING.
            move TEMP_STRING to GT_ITEM-CURRENCY.
          when 'Quantity'.
            move STRING to GT_ITEM-Quantity.
          when 'UoM'.
            move STRING to GT_ITEM-UoM.
        endcase.
      endif.
endcase.
if GV_NODETEXT = 'Header'.
    clear GV_HEADER.
elseif GV_NODETEXT = 'Item'.
    if GV_FIRST_TIME ne 'X'.
       append GT_ITEM.
     clear : gt_item.
       GT_ITEM-ITEMNO_ACC = gt_item-itemno_acc + 1.
    endif.
    GV_FIRST_TIME = ' '.
endif.
Get the next child
X_NODE = x_node->get_first_child( ).
Recurse
while not X_NODE is initial.
    perform GET_DATA tables     GT_ITEM
                     using      X_NODE
                     changing   GV_HEADER.
    X_NODE = x_node->get_next( ).
endwhile.
endform.
the XML file is:-
Thanx in advance

Error while uploading data in SAP (me01)using LSMW

Hi All,
I am using LSMW for the first time.
I am trying to upload data to the Source List transaction (me01) using batch input recording. I created a new recording through LSMW itself. My source structure consists of 5 fields:
<b>MATNR C(18)
WERKS C(4)
VDATU N(8)
BDATU N(8)
LIFNR C(10)
EKORG C(10)</b>
Now the problem is when i try to convert the data, it gives me an error saying
"For type "C",a maximum length specification of 65535 is allowed."
I have noticed that unlike Direct Input method,
using batch input does not give any fields in "Maintain Field Mapping & Conversion Rules". So even if I have my fields in my source structure ,there are no fields to which I can map them to.
I don't know that is how it is when we go with batch input.
My file contain data in following order:
DANGEROUS GOODS,ABBY,20060801,20060831,30010,TEST
Pls help me to solve this problem.

Hi Swapna!
You get such an error message, when define a constant and forget the second ':
g_werks = '1000. "wrong
g_werks = '1000'. "correct
In general: a batch input recording can have fixed values and some variables. You need to define, which fields you like to fill with a variable. Go to the overview of the recordings, open the recording in change mode and assign some variable names to the according batch lines.
<a href="http://help.sap.com/saphelp_erp2005vp/helpdata/en/76/a05b69e8a411d1b400006094b944c8/frameset.htm">Editing batch input recordings</a>
Follow the help for the following steps of structure assignments.
Regards,
Christian

Convert XML file to sap

Dear friends
              For converting XML file to SAP, I used TEXT_CONVERT_XML_TO_SAP function module. In this I have some doubt. Pls clarify this.
1. I am getting run time error with type h.
2 I_FIELD_SEPERATOR          = ';'
   I_LINE_HEADER              =
   I_TAB_RAW_DATA             =
   I_FILENAME                 =
   I_TOTALSIZE                =
for the above parameter what are the value has to passed.
Thanks.

Hi,
Take a look in this code:
*& Report z_xit_xml_check
REPORT z_xit_xml_check.
TYPE-POOLS: ixml.
DATA: BEGIN OF t_cabec OCCURS 0.
          INCLUDE STRUCTURE zmmt2010.
DATA END OF t_cabec.
DATA: BEGIN OF t_item OCCURS 0.
          INCLUDE STRUCTURE zmmt2011.
DATA END OF t_item.
DATA: BEGIN OF t_itemt OCCURS 0.
          INCLUDE STRUCTURE zmmt2012.
DATA END OF t_itemt.
TYPES: BEGIN OF t_xml_line,
          data(256) TYPE x,
        END OF t_xml_line.
DATA check_item(1).
DATA check_itemt(1).
DATA: l_ixml            TYPE REF TO if_ixml,
        l_streamfactory   TYPE REF TO if_ixml_stream_factory,
        l_parser          TYPE REF TO if_ixml_parser,
        l_istream         TYPE REF TO if_ixml_istream,
        l_document        TYPE REF TO if_ixml_document,
        l_node            TYPE REF TO if_ixml_node,
        l_xmldata         TYPE string.
DATA: l_elem            TYPE REF TO if_ixml_element,
        l_root_node       TYPE REF TO if_ixml_node,
        l_next_node       TYPE REF TO if_ixml_node,
        l_name            TYPE string,
        l_iterator        TYPE REF TO if_ixml_node_iterator.
DATA: l_xml_table       TYPE TABLE OF t_xml_line,
        l_xml_line        TYPE t_xml_line,
        l_xml_table_size TYPE i.
DATA: l_filename        TYPE string.
PARAMETERS: pa_file TYPE char1024 DEFAULT 'c:\xml.xml'.
START-OF-SELECTION.
    PERFORM busca_xml.
    PERFORM carrega_tabela.
*&      Form get_xml_table
FORM get_xml_table CHANGING l_xml_table_size TYPE i
                              l_xml_table      TYPE STANDARD TABLE.
Local variable declaration
    DATA: l_len      TYPE i,
          l_len2     TYPE i,
          l_tab      TYPE tsfixml,
          l_content TYPE string,
          l_str1     TYPE string,
          c_conv     TYPE REF TO cl_abap_conv_in_ce,
          l_itab     TYPE TABLE OF string.
    l_filename = pa_file.
upload a file from the client's workstation
    CALL METHOD cl_gui_frontend_services=>gui_upload
      EXPORTING
        filename   = l_filename
        filetype   = 'BIN'
      IMPORTING
        filelength = l_xml_table_size
      CHANGING
        data_tab   = l_xml_table
      EXCEPTIONS
        OTHERS     = 19.
    IF sy-subrc <> 0.
      MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
                 WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
    ENDIF.
ENDFORM.                    "get_xml_table
*&      Form process_dom
FORM process_dom USING document TYPE REF TO if_ixml_document.
    DATA: node      TYPE REF TO if_ixml_node,
          iterator TYPE REF TO if_ixml_node_iterator,
          nodemap   TYPE REF TO if_ixml_named_node_map,
          attr      TYPE REF TO if_ixml_node,
          name      TYPE string,
          prefix    TYPE string,
          value     TYPE string,
          indent    TYPE i,
          count     TYPE i,
          index     TYPE i.
    DATA v_codcat TYPE zmmt2011-codcat.
    DATA v_master_for TYPE zmmt2011-master_for.
    node ?= document.
    CHECK NOT node IS INITIAL.
    IF node IS INITIAL. EXIT. ENDIF.
create a node iterator
    iterator = node->create_iterator( ).
get current node
    node = iterator->get_next( ).
loop over all nodes
    WHILE NOT node IS INITIAL.
      indent = node->get_height( ) * 2.
      indent = indent + 20.
      CASE node->get_type( ).
        WHEN if_ixml_node=>co_node_element.
        element node
          name    = node->get_name( ).
          TRANSLATE name TO LOWER CASE.
          IF name = 'iten'.
            MOVE 'I' TO check_item.
          ENDIF.
          IF name = 'cabec'.
            MOVE 'C' TO check_item.
          ENDIF.
          IF name = 'iten_texto'.
            MOVE 'T' TO check_item.
          ENDIF.
          nodemap = node->get_attributes( ).
          IF NOT nodemap IS INITIAL.
          attributes
            count = nodemap->get_length( ).
            DO count TIMES.
              index = sy-index - 1.
              attr   = nodemap->get_item( index ).
              name   = attr->get_name( ).
              prefix = attr->get_namespace_prefix( ).
              value = attr->get_value( ).
            ENDDO.
          ENDIF.
        WHEN if_ixml_node=>co_node_text OR
             if_ixml_node=>co_node_cdata_section.
        text node
          value = node->get_value( ).
          IF check_item = 'C'.
            TRANSLATE name TO LOWER CASE.
            CASE name.
              WHEN 'lifnr'.     MOVE value TO t_cabec-lifnr.
              WHEN 'codcat'.
                MOVE value TO t_cabec-codcat.
                MOVE value TO v_codcat.
              WHEN 'bukrs'.     MOVE value TO t_cabec-bukrs.
              WHEN 'zterm'.     MOVE value TO t_cabec-zterm.
              WHEN 'waers'.     MOVE value TO t_cabec-waers.
              WHEN 'inco1'.     MOVE value TO t_cabec-inco1.
              WHEN 'inco2'.     MOVE value TO t_cabec-inco2.
              WHEN 'telf1'.     MOVE value TO t_cabec-telf1.
              WHEN 'verkf'.     MOVE value TO t_cabec-verkf.
              WHEN 'datav'.
                MOVE value TO t_cabec-datav.
                APPEND t_cabec.
            ENDCASE.
          ENDIF.
          IF check_item = 'I'.
            TRANSLATE name TO LOWER CASE.
            CASE name.
              WHEN 'master_for'.
                MOVE value TO t_item-master_for.
                MOVE value TO v_master_for.
              WHEN 'werks'.      MOVE value TO t_item-werks.
              WHEN 'versao'.     MOVE value TO t_item-versao.
              WHEN 'matkl'.      MOVE value TO t_item-matkl.
              WHEN 'j_1bindus3'. MOVE value TO t_item-j_1bindus3.
              WHEN 'j_1bmatuse'. MOVE value TO t_item-j_1bmatuse.
              WHEN 'j_1bmatorg'. MOVE value TO t_item-j_1bmatorg.
              WHEN 'j_1bnbmco1'. MOVE value TO t_item-j_1bnbmco1.
              WHEN 'bsgru'.      MOVE value TO t_item-bsgru.
              WHEN 'ekgrp'.      MOVE value TO t_item-ekgrp.
              WHEN 'txz01'.      MOVE value TO t_item-txz01.
              WHEN 'epstp'.      MOVE value TO t_item-epstp.
              WHEN 'netpr'.      MOVE value TO t_item-netpr.
              WHEN 'peinh'.      MOVE value TO t_item-peinh.
              WHEN 'meins'.      MOVE value TO t_item-meins.
              WHEN 'plifz'.      MOVE value TO t_item-plifz.
              WHEN 'mwskz'.      MOVE value TO t_item-mwskz.
              WHEN 'steuc'.
                MOVE value TO t_item-steuc.
                MOVE v_codcat TO t_item-codcat.
                APPEND t_item.
            ENDCASE.
          ENDIF.
          IF check_item = 'T'.
            TRANSLATE name TO LOWER CASE.
            CASE name.
              WHEN 'linha'.     MOVE value TO t_itemt-linha.
              WHEN 'txlng'.     MOVE value TO t_itemt-txlng.
                MOVE v_master_for TO t_itemt-master_for.
                MOVE v_codcat     TO t_itemt-codcat.
                append t_itemt.
            ENDCASE.
          ENDIF.
      ENDCASE.
    advance to next node
      node = iterator->get_next( ).
    ENDWHILE.
ENDFORM.                    "process_dom
*&      Form Busca_XML
      text
--> p1        text
<-- p2        text
FORM busca_xml .
    DATA: lc_mess(70) TYPE c,lv_tab.
    TYPES: BEGIN OF ty_zvmsgorgtr.
            INCLUDE STRUCTURE zmmt2011.
    TYPES   END OF ty_zvmsgorgtr.
Creating the main iXML factory
    l_ixml = cl_ixml=>create( ).
Creating a stream factory
    l_streamfactory = l_ixml->create_stream_factory( ).
    PERFORM get_xml_table CHANGING l_xml_table_size l_xml_table.
wrap the table containing the file into a stream
    l_istream = l_streamfactory->create_istream_itable( table =
    l_xml_table size = l_xml_table_size ).
Creating a document
    l_document = l_ixml->create_document( ).
Create a Parser
    l_parser = l_ixml->create_parser( stream_factory = l_streamfactory
                                      istream        = l_istream
                                      document       = l_document ).
Parse the stream
    IF l_parser->parse( ) NE 0.
      IF l_parser->num_errors( ) NE 0.
        DATA: parseerror TYPE REF TO if_ixml_parse_error,
              str        TYPE string,
              i          TYPE i,
              count      TYPE i,
              index      TYPE i.
        count = l_parser->num_errors( ).
        WRITE: count, ' parse errors have occured:'.
        index = 0.
        WHILE index < count.
          parseerror = l_parser->get_error( index = index ).
          i = parseerror->get_line( ).
          WRITE: 'line: ', i.
          i = parseerror->get_column( ).
          WRITE: 'column: ', i.
          str = parseerror->get_reason( ).
          WRITE: str.
          index = index + 1.
        ENDWHILE.
      ENDIF.
    ENDIF.
ENDFORM.                    " Busca_XML
*&      Form Carrega_Tabela
      text
--> p1        text
<-- p2        text
FORM carrega_tabela .
Process the document
    IF l_parser->is_dom_generating( ) EQ 'X'.
      PERFORM process_dom USING l_document.
    ENDIF.
ENDFORM.                    " Carrega_Tabela

Gettin data from SAP R/3 4.7 unicode sys to SAP ERP non-unicode sys via RFC

We are trying to get data from SAP R/3 4.7 unicode sys to SAP ERP non-unicode sys via RFC. We are reading field from the database via FM and this field got converted by SAP standard Method (CL_ABAP_CONTAINER_UTILITIES=>fill_CONTAINER_C) from structure. When reading this field from ERP sys and converted back to structure using SAP standard Method the value is un-accurate, and different(blank) giving values.
How, if the data originally was a char or numeric it works fine, but not for decimal.
best regards,
Abu-Qaht

I have a range fields with different type of ranges, am saving these to the database by converting them to a string via the same method. I got the same problem so I tried to convert the string to xstring using function SCMS_STRING_TO_XSTRING, before send it to the other system, but the function raised an exception: CX_SY_CONVERSION_CODEPAGE

Need to have 'variable name' node in the converted XML data.

i am converting the abap data to xml using cl_xml_document. in the converted xml data, i need to have one more node. in the below example, i want a node <variable name="productionOrderDetails"> to come after the Data node.
?xml version="1.0"?>
<Data>
     <item>
          <DISPO>100</DISPO>
          <PLNBEZ>F126</PLNBEZ>
          <GAMNG>300.000</GAMNG>
          <ERFMG>285.000</ERFMG>
          <PRE_PROD>100.000</PRE_PROD>
          <PRE_BLOG>0.000</PRE_BLOG>
          <BLOG_MTD>144.000</BLOG_MTD>
          <BAL_PLAN>144.000</BAL_PLAN>
     </item>
</Data>
thanks in advance

Hi ,
you can use class IF_IXML_NODE, first you need to read (go thru ) XML then need to Insert a New Node.
ref SAP Program BCCIIXMLT1/BCCIIXMLT*
regards
Prabhu

Convert tally data to SAP B1

Similar Messages

Maybe you are looking for