Transaction links to gl

hi experts
I need to create every single transaction link to its own module and for that i see that gl_je_lines, gl_import_references, gl_je_hearders are the the table which store every transaction reference in it.
but how can i track each transaction to dril down to it main transations.
for e.g. lets suppose .
if i see one set of transaction of sales invoice in which
1- entry to customer for generate a/r
2- entry to sales for sales credit
3- tax, entries ,
4- stock movements
well for BUSSINESS INTELLIGENCE ( if i dont have BI FOR APPS) and i m working on standard BI tool then i have to create ETLs for that and for that i need to link every single transaction to its own module and tables.
is there anyone who can help me in this regards
simplly i just want to link every single line from gl_je_lines from its own module table ... ( e.g) gl_je_line link to ra_customer_trx_lines, or gl_je_lines link to mtl_material_transactions
how can i do that .. please help me out .. give me any solutions .. its urgent and would be highly appriciatbale..
regards
Anwer

Hi,
If you have updated your legacy GL account No. in "Alternative account No" field in the SAP GL account,
1. T Code SE16, Table Name SKB1, display the field ALTKT (your legacy GL account).
2. Go to any T Code where the GL account option is available(F-02, FB01, FB50, FS00, etc.,), press F4, select the tab "Alternative account number" , and give the old legacy GL No., it will give the new GL account number.
If you have used different field, let me know the field name to answer your question
Hope it helps
Saravanan.A

Similar Messages

  • Account Details page transaction link do not display anything

    Hi,
    I extended the TransactionTableVO to include new columns. Initially, whenever I click on the transaction link, I get an exception error. But I fixed it by commenting out functions that seem to overrride the original one (like setIrSalesOrder, setAmountDueRemainingFormatted etc). It worked for Payment transaction type but not for the other types like Credit Memo, Chargeback, Invoice, Debit Memo, etc.
    This Transaction link displays different pages according to the transaction type. I don't have any clue why it worked for Payment transaction type but did not work for the rest. There is no error just blank content.
    I opened the original TransactionTableVORowImpl.class and found the following code possibly related to this issue:
    public static String getStaticTransactionDetailsRegionCode(InvoiceTableVORowImpl invoicetablevorowimpl, String s)
    String s1 = null;
    if("INV".equals(s) || "GUAR".equals(s) || "CB".equals(s) || "DM".equals(s) || "DEP".equals(s))
    s1 = "ARITRANSACTIONDETAILSPAGE";
    } else
    if("CM".equals(s))
    s1 = "ARITEMPCMDETAILSPAGE";
    } else
    if("PMT".equals(s))
    s1 = "ARI_PAYMENT_DETAILS_PAGE";
    } else
    if("REQ".equals(s))
    s1 = "ARITEMPCMREQUESTDETAILSPAGE";
    return s1;
    public void setTransactionDetailsRegionCode(String s)
    setAttributeInternal("TransactionDetailsRegionCode", s);
    I checked the URL and it does contain the correct name of the page i.e. if it's an Invoice transaction type, it includes ARITRANSACTIONDETAILSPAGE in the URL. So it is getting the correct page to redirect to. The window title, however, contains the following:
    Message not found. Application: AR, Message Name: nullTitle
    Any assistance is greatly appreciated!
    N
    Edited by: pekochan on 25/11/2009 09:43

    I think I'm not passing the correct paramaters. I checked the URL and it's not passing any &Irtransactiontype. How can I check where this parameter is coming from??

  • Transaction linking, Monitoring and Alerting product

    Hi,
    I wanted to check if there is any product from BEA Systems which can be used to
    capture meta data at different points in a business transaction...The business
    process could be a multi hop process...Meta data from one hop to another can usually
    be linked with some attributes and some times the linking algorithm can be complex...
    We are investigating if there are any products which can be used to capture the
    transaction attributes, perform the linking between the meta data at different
    hops and also where we can specify some business rules like if we don't have matching
    data at some hops for a transaction flow to perform some altering function...So
    the product will be doing some transaction monitoring activity...
    If anyone has any information about this kind of software please let me know...
    Thanks
    Surajit

    Hi Ralph,
    We are facing the same issue is our system. I have checked the specified note and observed that few of the systems had to be updated in Managed System Configuration. I have updated the systems. But, the alerts have not stopped.
    Can you please tell me the procedure to resolve this issue?
    Thanks.
    Regards,
    Deepika R

  • Custom transaction link in EP screen for buyer

    Hi all,
    We are on SRM 5.0 Sp12.
    Our users use EP as the fornt end.Now we have a custom transction for a custom report created in SRM and would have the link to it in EP screens for PUCRAHSER role.Can snybody suggest if this is possible?If so,how??
    I knw its possible to put the custom link if we log in thorugh the BBPSTART url in IE.But i need to know what are the options if we need to have this link in EP?
    Thanks.

    Hi jay,
    Can you please exaplin the steps to create an iview and embed them in a SRM role.

  • Transaction link in CR report

    Hello to All,
    I am working on CR report using Hyperlink utility
    'http://$b1$/link?table=OCRD&key='+Cstr({OPOR.CardCode})
    It is working fine .(it open Business Partner Master Form)
    But when i want to open purchase table form CR report then change
    'http://$b1$/link?table=OPOR&key='+Cstr({OPOR.DocNum})
    It show error You have not authorized open this form  And login user is superuser with Profesional licence.
    Please suggest me for same.
    Thanks
    Manvendra Singh Niranjan

    Solved
    Using This
    'http://$b1$/link?table=OPOR&key=' + totext({OPOR.DocEntry},0,"","")

  • Modifying MB01, Could affect other transaction linked to it?

    Hi Experts,
    My user is encountering this error when she tried to define the delivery amount or qty.. and post it. I'm just wondering why they were able to post a GR before July even the amount is 7 digits. The user tried to breakdown the amount but there's still an error.
    There was no changes in the configuration or any user exits connected to it. I have checked the runtime error logs in st22 and released it. But until now those errors ar still in the list.
    My last option is to change the data type of Rexwrt field from EXWRT to wertv12. Exwert has a length of 13 characters and I want to change it to WERTV12 that has 23 characters.
    they are using SAP release 4.0:
    007650 DATA: REXWRT LIKE EXWRT.
    > REXWRT = W-EXWRT + W-SALK3.
    from SAP 6
    DATA: rexwrt TYPE wertv12.
    My question is, Would it be safe if I modify it? How would I know if there are other transaction may affect this code?
    I don't get an error in DEV server.
    Overflow when converting from "1.08844e+013"
    What happened?
    The current ABAP/4 program "SAPLMBGB " had to be terminated because
    one of the statements could not be executed.
    This is probably due to an error in the ABAP/4 program.
    What can you do?
    Print out the error message (using the "Print" function)
    and make a note of the actions and input that caused the
    error.
    To resolve the problem, contact your
    SAP system administrator.
    Error analysis
    When attempting to convert the value "1.08844e+013",
    an overflow occurred.
    There is probably an error in the program
    "SAPLMBGB ".
    How to correct the error
    Probably the only way to eliminate the error is to correct the program.
    You may able to find an interim solution to the problem in the
    SAP note system. If you have access to the SAP note system yourself,
    please use the following search criteria:
    "CONVT_OVERFLOW"
    "SAPLMBGB " or "LMBGBFSU "
    "WERT_V_RECHNEN"
    If you cannot solve the problem yourself, please send the
    following documents to SAP:
    1. A hard copy print describing the problem.
       To obtain this, select the "Print" function on the current screen.
    2. A suitable hardcopy prinout of the system log.
       To obtain this, call the system log with Transaction SM21
       and select the "Print" function to print out the relevant
       part.
    3. If the programs are your own programs or modified SAP programs,
       supply the source code.
       To do this, you can either use the "PRINT" command in the editor or
       print the programs using the report RSINCL00.
    4. Details regarding the conditions under which the error occurred
       or which actions and input led to the error.
    System environment
    SAP Release.............. "40B"
    Application server....... "prosap"
    Network address.......... "192.168.0.80"
    Operating system......... "Windows NT"
    Release.................. "0"
    Hardware type............ "PENTIUM"
    Database server.......... "prosap"
    Database type............ "INFORMIX"
    Database name............ "PRO"
    Database owner........... "sapr3"
    Character set............ "E"
    SAP kernel............... "40B"
    Created on............... "May 25 1999 02:20:08"
    Created in............... "NT 4.0 1381 Service Pack 3 x86 MS VC++ 11.00?"
    Database version......... "inf INF_723_TC2"
    Patch level.............. "400"
    Patch text............... " "
    Supported environment....
    Database................. "INFORMIX 7.2*.*"
    SAP database version..... "40B"
    Operating system......... "Windows NT 0 4"
    User, transaction...
    Client.............. 400
    User................ "SAPUSR_FI05"
    Language key........ "E"
    Transaction......... "MB01 "
    Program............. "SAPLMBGB "
    Screen.............. "SAPMM07M 0210"
    Screen line......... 71
    Information on where termination occurred
    The termination occurred in the ABAP/4 program "SAPLMBGB " in
    "WERT_V_RECHNEN".
    The main program was "SAPMM07M ".
    The termination occurred in line 779
    of the source code of program "LMBGBFSU " (when calling the editor 7790).
    Source code extract
    007490                             W-BETRAG LIKE BETRAG.
    007500
    007510     DATA: RMENGE LIKE MENGE.
    007520     RMENGE = 0 - W-MENGE.
    007530     IF ( W-EXWRT IS INITIAL AND W-EXWOB IS INITIAL ) OR
    007540        ( W-LBKUM < 0 AND ( W-SHKZG = H OR W-LBKUM < RMENGE ) ).
    007550       PERFORM WERT_WERTPROPORTIONAL USING W-SALK3
    007560                                           W-VERPR
    007570                                           W-LBKUM
    007580                                           W-PEINH
    007590                                           W-MENGU
    007600                                           W-WERTU
    007610                                           W-BWSPA
    007620                                           W-MENGE
    007630                                           W-BETRAG.
    007640     ELSE.
    007650       DATA: REXWRT LIKE EXWRT.
    007660       IF W-SHKZG = H.
    007670         IF ( W-LBKUM > W-MENGE AND NOT W-SALK3 < W-EXWRT )
    007680            OR NOT W-LBKUM > 0.
    007690           W-BETRAG = W-EXWRT.
    007700         ELSEIF NOT W-LBKUM < W-MENGE.
    007710           W-BETRAG = W-SALK3.
    007720         ELSE.
    007730           RMENGE = W-MENGE - W-LBKUM.
    007740           W-BETRAG = ( RMENGE * W-EXWRT ) / W-MENGE.
    007750           W-BETRAG = W-BETRAG + W-SALK3.
    007760         ENDIF.
    007770       ELSE.
    007780         RMENGE = W-MENGE + W-LBKUM.
    ----->         REXWRT = W-EXWRT + W-SALK3.
    007800         IF ( RMENGE < 0 AND NOT REXWRT > 0 )
    007810            OR NOT W-LBKUM < 0.
    007820           W-BETRAG = W-EXWRT.
    007830         ELSEIF NOT RMENGE > 0.
    007840           W-BETRAG = 0 - W-SALK3.
    007850         ELSE.
    007860           W-BETRAG = ( RMENGE * W-EXWRT ) / W-MENGE.
    007870           W-BETRAG = W-BETRAG - W-SALK3.
    007880         ENDIF.
    007890       ENDIF.
    007900       IF W-BETRAG > MAXIMUM OR W-BETRAG < MINIMUM.
    007910         MESSAGE E302 WITH 'WERT_V_RECHNEN' 'W-BETRAG'.
    007920       ENDIF.
    007930     ENDIF.

    Hi Maui,
    See SAP Note
    Note 196607 - Overflow in WERT_V_RECHNEN provided by SAP on 25.01.2000 .
    the correction instruction clearly mentions
    Context Block 
        PERFORM WERT_WERTPROPORTIONAL USING W-SALK3
                                            W-VERPR
                                            W-LBKUM
                                            W-PEINH
                                            W-MENGU
                                            W-WERTU
                                            W-BWSPA
                                            W-MENGE
                                            W-BETRAG.
      ELSE.
    Delete Block 
        DATA: REXWRT LIKE EXWRT.
    Insert Block 
    DATA: REXWRT TYPE WERTV12.
    Hope this helps you. Revert for more clarifications if any.
    <b>Always reward points to useful suggestion.</b>
    regards,
    Vikas

  • Using VO Attribute in destination URI of Item Style LINK in OAF Personalization

    Extended the VO in iReceivables to have a Transaction link (external URL) as additional view attribute 'InvoiceUri' (i.e. each TRX will have a unique URL from 3rd party)
    Now trying to add a LINK type Item in the same and proving the VO Attribute as Destination URI, tried all the below possibilities:
    javascript:void window.open('decodeURIComponent({@InvoiceUrl})')
    javascript:void window.open('{@InvoiceUrl}')
    {@InvoiceUrl}
    When I click the link item created/added using personalization is, its opening the URL like this:
    http://*******.com:34604/OA_HTML/https%3A%2F%2Fxxxx.net%2FXDSServer%2FInvoice_51214777_20141201.pdf
    First issue is its prefixing the Oracle Apps server url (i.e. http://*******.com:34604/OA_HTML/) to the invoice url while opening the new IE window
    Other issue is URL being encoded i.e. removing all the special characters and replacing them with %3A, %2F etc.,
    Is there a way to make it work, with out extending the page controller. This is for Oracle R12.1.3, tried with IE 7, 11 and Mozilla
    Thanks in advance

    Hi,
    In destination URI, you can add parameters at the end of URI as shown below:
    OA.jsp?page=/xx/oracle/apps/<app_name>/webui/XxPageNamePG&Action=DETAILS&HdrId={@HeaderId}
    Here, there are 2 parameters added (followed by '&'):
    Action - event name
    HdrId - parameter name you want to pass.
    {@HeaderId} - value of parameter (VO attribute name)
    --Sushant                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

  • Transaction Launcher

    Hi,
    I have some doubts while launching the non-bsp url through transaction launcher.
    Question1. What is the significance of Get/Post method while defining the Non-bsp URL?
    I just added the Google Search link in my left navigation bar.
    When we "Define URLs and Parameters"
    (spro->crm->ui_framework->technical_role_definition->transaction_lanucher->define urls and parameters)
    I select the Post method. But when I clicked on the Google Search link in the Left Navigation Bar, it showed the error "Post method is NOT relevant for URL". I deleted the URL link and defined it again without any selecting method and it worked fine.
    Question2. Can we pass the parameter when Launch Transaction type is "URL transaction"? How many no of parameter can be passed and how?
    Thanks,
    Anup

    Thirumala,
    Trying to follow your logic here. I have created a Webdynpro app. We have CRM 7.0 and what I need to do is pass to the webdynpro app the sales doc number. Created a URL for the application with a parameter. Also created a transactional link with a parameter which I named the same the parameter value is //datacontextCURRENTCUSTOMER/BuilR3LastSalesDocRel/DOCNUMBER. You say to set this value and the parameter would be set automatically? Do I have to do some manipulation before you navigate to the application? Is there another way to set the value? Example:
    data: lv_navigation   type ref to  if_crm_ui_navigation_service,
              lo_link      type ref to if_bol_bo_property_access,
              data_collection  type ref to if_bol_bo_col.
        lo_link ?= cl_crm_uiu_bt_param_create=>if_ui_link_parameter_class~create_parameter_object(
                                                iv_link_id   = 'BILLINGDOC'
                                                iv_parameter = '0214396560' ).
        create object data_collection type cl_crm_bol_bo_col.
        data_collection->add(
                iv_entity    = lo_link
                iv_set_focus = abap_true ).
        lv_navigation = cl_crm_ui_navigation_service=>get_instance( me ).
        lv_navigation->navigate( iv_link_id = 'ZSLS-INV'
                                  iv_data_collection = data_collection ). "#EC NOTEXT UIF_PERS

  • Report linking  Delivery , Receipts , Purchase Return & Sales Return Entry

    We have Service Contract for Supplying Inventory to Our Indirect Customer.
    For Example:We have signed service contract with  IBM whose customer is Bank of India, now once Bank of India logs any complaint call to IBM for faulty part, IBM ask us to supply new part from our inventory to Bank of India and collect faulty part from Bank of  India, after inward of faulty part from bank of India we then send same faulty part to IBM against which IBM send us the new part hence the cycle gets completed and our inventory regain its level after four transaction.
    Each of Inventory in this transaction is managed serially
    To cater to this business scenario, we prepared Delivery Transaction against Bank of India(Bank of India is defined as customer)(For Serial no abcd1234) and prepared  sales return entry of faulty from Bank of India (For serial no pqrs6789), then prepared goods return entry (For Serial no pqrs6789) against IBM (IBM is defined as vendor) and in last prepared GRPO entry for inward of Inventory from IBM.
    In this scenario any transaction can be initiated first.
    Across all this transaction one No (RMA no  a UDF) is common same for all transaction
    So to have complete tracking of this we want to linked all this transaction i.e for one RMA no report should show all transaction linked in single row including serial no of item.
    Satish

    Hi
    Pls find the below query which i have used
    {select * from (select 'GRN' as doc_type,a.docdate,a.docnum,a.u_rmano,a.numatcard,a.cardcode,a.cardname,a.docstatus,c.itemcode,c.itemname,
    c.whscode,b.quantity,status,case when c.direction=0 then 'Inward' when c.direction=1 then 'Outward' end as direction ,d.intrserial,d.suppSerial,d.Batchid
    from opdn a inner join pdn1 b on a.docentry=b.docentry
    inner join (select * from sri1 where basetype=20) c
    on a.docnum=c.basenum and b.itemcode=c.itemcode
    inner join (select * from osri where basetype=20) d
    on a.docnum=d.basenum and b.itemcode=d.itemcode
    where not a.u_rmano is null) grn
    left outer join
    (select 'DC' as doc_type,a.docdate,a.docnum,a.u_rmano,a.numatcard,a.cardcode,a.cardname,a.docstatus,c.itemcode,c.itemname,
    c.whscode,b.quantity,status,case when c.direction=0 then 'Inward' when c.direction=1 then 'Outward' end as direction ,d.intrserial,d.suppSerial,d.Batchid
    from odln a inner join dln1 b on a.docentry=b.docentry
    inner join (select * from sri1 where basetype=15) c
    on a.docnum=c.basenum and b.itemcode=c.itemcode
    inner join (select * from osri where basetype=20 or basetype=58 or basetype=16 or basetype=67 or basetype=15 ) d
    on c.sysSerial=d.sysSerial and c.itemcode=d.itemcode
    where not a.u_rmano is null) dc
    on grn.u_rmano=dc.u_rmano
    left outer join
    (select 'SR' as doc_type,a.docdate,a.docnum,a.u_rmano,a.numatcard,a.cardcode,a.cardname,a.docstatus,c.itemcode,c.itemname,
    c.whscode,b.quantity as  srqty,status,case when c.direction=0 then 'Inward' when c.direction=1 then 'Outward' end as direction ,d.intrserial,d.suppSerial,d.Batchid,1 as [quantity]
    from ordn a inner join rdn1 b on a.docentry=b.docentry
    inner join (select * from sri1 where basetype=16) c
    on a.docnum=c.basenum and b.itemcode=c.itemcode
    inner join (select * from osri where basetype=20 or basetype=58 or basetype=16 or basetype=67 or basetype=15 ) d
    on c.sysSerial=d.sysSerial and c.itemcode=d.itemcode
    where not a.u_rmano is null
    ) sr
    on grn.u_rmano=sr.u_rmano
    left outer join
    (select 'PR' as doc_type,a.docdate,a.docnum,a.u_rmano,a.numatcard,a.cardcode,a.cardname,a.docstatus,c.itemcode,c.itemname,
    c.whscode,b.quantity as prQty,status,case when c.direction=0 then 'Inward' when c.direction=1 then 'Outward' end as direction ,d.intrserial,d.suppSerial,d.Batchid,1 as [quantity]
    from orpd a inner join rpd1 b on a.docentry=b.docentry
    inner join (select * from sri1 where basetype=21) c
    on a.docnum=c.basenum and b.itemcode=c.itemcode
    inner join (select * from osri where basetype=20 or basetype=58 or basetype=16 or basetype=67 or basetype=15 ) d
    on c.sysSerial=d.sysSerial and c.itemcode=d.itemcode
    where not a.u_rmano is null) pr
    on grn.u_rmano=pr.u_rmano}

  • Request: option to link invoice to payment for SBO 2007A

    Hi all,
    The situation is as follows:
    A payment on account is booked. Customer wants to link an invoice to that payment afterwards. In version 2007 the transaction 'link payments to invoices' has disappeared compared to version 2005.
    It's possible to do an internal reconciliation, but then that payment is not linked to the invoice,  i.e. the payment is not listed in the payment history of the invoice.. It should be possible to link a payment on account to an invoice.
    We have logged a message with SAP but must raise a DRQ ( Development Request) as the function is not there anymore.
    Looking forward to a proper solution!
    Kind regards,
    Charlotte Jansen
    SAP Business One consultant

    The query is linked to the BP via en UDF and a FMS and is as follows:
    SELECT '' AS Type, '' AS 'CustName', NULL AS 'Doc No', NULL AS 'Doc Date', '' AS 'Curr',NULL AS 'Amount', NULL AS 'Due date',  '' AS 'Status',  '' AS 'PayCurr', 0 AS 'Paid', NULL AS 'Date paid', NULL AS 'Ref.', NULL AS 'Pay days',NULL AS Late
    UNION SELECT
    'Fact' AS Type,
    T0.CardName AS 'CustName',
    T0.DocNum AS 'Doc No',
    T0.DocDate AS 'Doc Date',
    T0.DocCur AS 'Curr',
    Amount=CASE T0.DocCur
       WHEN 'EUR' THEN T0.DocTotal ELSE  T0.DocTotalFC END, T0.DocDueDate AS 'Due date', T0.DocStatus AS 'Status', T1.DocCurr AS 'PayCurr', Paid=CASE T0.DocCur
       WHEN 'EUR' THEN T0.PaidToDate ELSE  T0.PaidFC END, T1.TrsfrDate AS 'Date paid', T0.ReceiptNum AS 'Ref.',
    DATEDIFF(dd,T0.DocDueDate,T1.TrsfrDate) AS 'Pay days', Late=CASE T0.DocStatus
       WHEN 'O' THEN DATEDIFF(dd,T0.DocDueDate,getdate())
       WHEN 'C' THEN DATEDIFF(dd,T0.DocDueDate,T1.TrsfrDate) END FROM [dbo].[OINV] T0 LEFT OUTER JOIN [dbo].[ORCT] T1 ON T1.DocNum = T0.ReceiptNum WHERE T0.CardCode=$[$-5.0.0]
    UNION SELECT
    'Cred.fact' AS Type,
    T2.CardName AS 'CustName',
    T2.DocNum AS 'Doc No',
    T2.DocDate AS 'Doc Date',
    T2.DocCur AS 'Curr',
    Amount=CASE T2.DocCur
       WHEN 'EUR' THEN T2.DocTotal-1 ELSE  T2.DocTotalFC-1 END, T2.DocDueDate AS 'Due date', T2.DocStatus AS 'Status', T3.DocCurr AS 'PayCurr', Paid=CASE T3.DocCurr
       WHEN 'EUR' THEN T3.DocTotal ELSE  T3.DocTotalFC END, T3.TrsfrDate AS 'Date paid', NULL AS 'Ref.',
    DATEDIFF(dd,T2.DocDueDate,T3.TrsfrDate) AS 'Pay days', Late=CASE T2.DocStatus
       WHEN 'O' THEN DATEDIFF(dd,T2.DocDueDate,getdate())
       WHEN 'C' THEN DATEDIFF(dd,T2.DocDueDate,T3.TrsfrDate) END FROM [dbo].[ORIN] T2 LEFT OUTER JOIN [dbo].[ORCT] T3 ON T3.DocNum = T2.ReceiptNum WHERE T2.CardCode=$[$-5.0.0]
    UNION SELECT
    'Part.Paym.' AS Type,
    T4.CardName AS 'CustName',
    T4.DocNum AS 'Doc No',
    T4.DocDate AS 'Doc Date',
    T4.DocCurr AS 'Curr',
    Amount=CASE T4.DocCurr
       WHEN 'EUR' THEN T4.DocTotal-1 ELSE  T4.DocTotalFC-1 END, NULL AS 'Due date', '*' AS 'Status', T4.DocCurr AS 'PayCurr', Paid=CASE T4.DocCurr
       WHEN 'EUR' THEN T4.DocTotal ELSE  T4.DocTotalFC END, T4.TrsfrDate AS 'Date paid', NULL AS 'Ref.', NULL AS 'Pay days', NULL AS ' Late '
    FROM [dbo].[ORCT] T4
    WHERE T4.CardCode=$[$-5.0.0] AND T4.PayNoDoc='Y'
    ORDER BY Status DESC, 'Due date' ASC, Type ASC

  • Add extra link to Go Shopping screen

    Hi Guys.
    SRM 4.0, server 5.0, standalone ITS.
    Is there an easy way to add an extra transaction/link to the basic screen of SRM? I am thinking the template
    bbpstart/99/bbpglobal_650.html
    This is for example the first screen in my SRM, and I also need the function "Process Purchase order" to appear on this screen along with Go Shopping, Goods Receipt, Status etc.
    Is the only way to do this by changing the web template through SE80?
    Thanks for info.
    BR
    Dennis

    Hi
    <b>What is the purpose behind adding this new link ? What's the detailed business  requirment in your case ? Is this is related to Catalog type of link functionality ?</b>
    Which SRM version are you using ?
    <u>Anyways, please go through the following pointers, which will guide -></u>
    Re: Add Custom link in Home Page
    Add catalog link in Describe Requirement
    Re: Want to add one more link in the first screen when user gets into EBP
    Regards
    - Atul

  • View selecion problem in MM12 transaction

    Hi,
      In my bdc program I want to directly select 'Costing View1' in MM12 transaction.
      Is there any function module available for this??
      Please help me.
    Regards,
    Tintu

    Hi Kevin,
    Thanks for your response, I have exported and tried in other 12.0 &12.1system's  too then also Transaction properties are not visible.
    The transaction is not generating any warning message of failure, but the Transaction link editor window will be hanged once i click on that tab.(This hanging of window is done only for the  transactions exported  from 12.1 to 12.0)
    Regards,
    Sireesha.
    Edited by: sireesha.g on Feb 3, 2011 8:34 PM
    Edited by: sireesha.g on Feb 3, 2011 8:36 PM

  • Problem in Orange Arrow Link

    Dear All,
    I have a typical problem which I am facing it for the first time.
    I have created a report which shows transactions listing of the branches in the system i.e Sales Order, Delivery, Invoice etc. Each transaction heads are a sub report i.e Invoice is a subreport, Order is a subreport and so on. I have included the link button also so that the users can go into the transactions when they preview the report. Now the link button is working for all the documents except for the Invoices where it throws the message "You are not permitted to perform this transaction". Now there is no authorization involved in the database. Everyone has a full authorization.Even I myself as a manager(super user) cannot open the transaction from the link arrow. If i go manually to Invoice, I am able to open the document. Now the same report when I open up in another database i.e OEC one it is working.
    Please can anyone let me know where I am missing something or where I am going wrong.
    FYI, the report has a selection of Branches, From Date and To Date and i am using SAP 8.8 Pl 10.
    Regards,
    Gary

    Hi Gary,
    Refer This Link,
    Transaction link in CR report
    Thanks,
    Srujal Patel

  • Reg passing values to a link

    Hi all,
    Is it possible to pass values to a link. The requirement is i need to pass some values to a standard transaction link and the values which i pass should go to the respective fields of the link.
    Can anyone suggest?
    Thanks and Regards,
    Sneha.

    here is a sample code to pass values to yahoo loging screen and logging on to it from your BSP
    <%@page language="abap" %>
    <%@extension name="htmlb" prefix="htmlb" %>
    <htmlb:content design="design2003" >
      <htmlb:page title=" " >
        <htmlb:form method = "POST"
                    action = "https://login.yahoo.com/config/login?" >
          userid
          <htmlb:inputField id="login" />
          <br>
          password
          <htmlb:inputField id       = "passwd"
                            password = "true" />
          <br>
          <htmlb:button id      = "test"
                        text = "login"
                        onClick = "myonclick" />
        </htmlb:form>
      </htmlb:page>
    </htmlb:content>
    Regards
    Raja

  • Storing of HR documents with archive link in DMS?

    hi experts,
    how to store HR documents with archive link in DMS?
    i found somewhere it is possible with tr. code OAWD,OAAD
    is helpful..or is there any other way for storing HR documents
    becz i am not able to do it..
    if any one guide me it will be very helpful to me.
    thx..pts will be awarded be sure..

    hi sam ra,
    SAP ArchiveLink - Scenarios in
    Applications (BC-SRV-ARL)
    SAP ArchiveLink® is one of the SAP Basis cross-application communication interfaces between
    the SAP System and external components. External components may be general desktop
    applications or external storage systems. The integration of SAP ArchiveLink in the various SAP
    applications enables the storage scenarios explained in this cross-application documentation.
    The documentation is structured as follows:
      An Introductory Section  (Seite 10) containing general information about storing using SAP
    ArchiveLink and about the following documentation
      An application-specific section for each SAP application component (for example, FI, SD,
    HR) with the relevant storage scenarios
    For information on related areas, see the following documentation:
      SAP ArchiveLink  (Extern)
      SAP Business Workflow  (Extern)
      Archiving and Deleting Application Data  (Extern)
    SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
    SAP ArchiveLink - Introduction
    April 2001 9
    SAP ArchiveLink - Introduction
    The following sections contain general information about this scenarios documentation.
    SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
    SAP ArchiveLink and Application Scenarios
    10 April 2001
    SAP ArchiveLink and Application Scenarios
    SAP ArchiveLink® is one of the integrated interfaces in the SAP Basis System that can be used
    to store all kinds of documents in external content servers.
    SAP ArchiveLink therefore complements the existing range of SAP application software. For a
    detailed description of SAP ArchiveLink, see Introduction to SAP ArchiveLink  (Extern).
    The SAP application components, for example, SD, FI, HR and MM, support storing using SAP
    ArchiveLink by providing various application scenarios. Inbound documents, outbound
    documents, print lists, archive files, desktop files and binary files are supported.
    How the inbound documents are entered in the system and forwarded for processing and storing
    depends on the storage scenario used. For information about the possible Storage Strategies
    (Extern) , see the documentation SAP ArchiveLink  (Extern).
    This documentation describes the storage scenarios that are integrated in the SAP applications,
    for example, how Sales and Distribution (SD) documents can be stored in external storage
    systems using SAP ArchiveLink.
    Archiving in databases using the ADK (Archive Development Kit) is not the same as
    storing using SAP ArchiveLink.
    For informationen about data archiving using the ADK archiving transaction, see the
    documentation Archiving and Deleting Application Data  (Extern).
    SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
    SAP ArchiveLink: Overview
    April 2001 11
    SAP ArchiveLink: Overview
    Background
    There is a growing trend nowadays to transfer stored data from paper/microfiche to external
    “content servers” (for example, archives). Companies are obliged by law and/or internal
    standards to keep documents for a certain length of time. Traditionally, paper archives or
    microfilms have been used, but these methods are very expensive, either due to copying costs or
    the large amount of space required by such archives. By contrast, electronic storing methods are
    a much cheaper option and represent an important part of the “paperless office” concept.
    SAP’s R/3 System supports a variety of business processes, which can involve documents both
    in paper form and in electronic form. The documents either serve to trigger all kinds of processing
    steps in FI, SD, HR and so on, or they are documents relating to processes in one of these
    application areas.
    When linked to SAP applications, content servers and the SAP ArchiveLink interface allow
    flexible access to all document searches available in the SAP System and can therefore lead to
    considerable time savings. In addition, a combination of the SAP System and SAP ArchiveLink
    allows users multiple access (parallel and direct) to stored documents from their work center
    without the need for time-consuming searches, which guarantees faster access to documents.
    The subsequent sections of this documentation describe the integration of SAP ArchiveLink in
    the functions of various application components within the SAP System.
    Concept
    SAP ArchiveLink provides the following interfaces:
      User interface
      Application Interface
    This interface consists of function modules, which must be integrated in the SAP
    applications, if SAP ArchiveLink functions are to be used.
    Business objects are linked to stored documents and object methods are available that
    allow storing using SAP ArchiveLink to be integrated flexibly in SAP Business Workflow.
      Interface between SAP and external components and general desktop applications
    External components may be HTTP content servers, for example. General desktop
    applications may be MS Word and MS Excel, for example.
    Positioning SAP ArchiveLink
    SAP ArchiveLink enables
      Incoming documents to be stored in the SAP System
      Information from the SAP System (for example, outgoing documents and print lists) to be
    stored
      Direct access from SAP application components to stored documents
      Integration of external content servers with the SAP System
    SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
    SAP ArchiveLink: Overview
    The SAP ArchiveLink-specific Terms  (Extern) “document”, “technical document class”, “document
    type”, “object type” and “synchronous storing” and “asynchronous storing” are explained in the
    SAP ArchiveLink documentation, which also contains information on the Administration Concept
    (Extern) (content servers, links and link tables).
    Technical Basis
    Links from documents to business objects are created by the generation of a link table entry,
    which contains both a unique identification for each business object using the object type and
    object key and a reference to a stored document using the content server ID and a unique key for
    each document stored in this content server. It is therefore possible to create a link between a
    business object and any number of documents using a simple 1:n relationship in a table. No
    entry is required in the application tables in which the business objects are managed. If the link
    table entry for an stored document is deleted, all references in the SAP System to this stored
    document are also deleted. This technique allows the options for accessing stored documents to
    be integrated flexibly into the SAP System.
    Application Interface
    The interface to the SAP applications contains the following functions:
      Linking business objects with stored documents
    This function is used to display, retrieve or store stored documents directly from the
    business object. An example of this is the link between an F1 business object invoice
    and original invoices that have been scanned into the system.
      Linking business objects with stored outgoing documents
    This function is used to store documents generated using SAPscript and link them with
    the relevant business objects. Examples of documents are outbound quotations, order
    confirmations, purchase orders and invoices.
      Storing print lists
    The process for storing print lists is the same as for outgoing documents.
    As of R/3 Release 4.6C, application objects archived in data archiving (ADK) are not
    stored using SAP ArchiveLink, but rather using the Content Management Service
    (Extern) of the SAP Knowledge Provider  (Extern) (KPro).
    Integration Status
    Many applications in the SAP System are linked directly or indirectly with SAP ArchiveLink:
      Direct link
    – FI
    – MM
    – SD
      Indirect link
      Via the DMS (document management system): MM, PP,...
    SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
    SAP ArchiveLink: Overview
    April 2001 13
    SAP ArchiveLink is centrally integrated in the DMS and all applications with object
    links to the DMS are therefore linked to SAP ArchiveLink.
      Via MC (Message Control): MM, SD,...
    The integration of SAP ArchiveLink in message control allows outgoing documents to
    be stored.
      Via SAPconnect and the Business Workplace: Faxes
    Inbound faxes can be processed directly in the Business Workplace, stored and
    linked with business objects without having to be printed first.
    Generic Object Services
    For R/3 Release 4.0A, generic object services are provided for four SAP ArchiveLink
    functions via the system menu for all SAP applications.
    From the business objects implemented in the SAP applications, four SAP ArchiveLink functions
    can be executed in all applications and independently of which application is involved:
      You can display the hit list of stored documents
      You can assign stored documents subsequently to a business object.
      You can store documents in dialog
      You can create a bar code for a business object
    These functions are integrated into all SAP applications via object services. There is no need for
    special function modules to be integrated in the applications. For more information, see Generic
    Object Services  (Extern).
    For these functions to work smoothly, object orientation in the SAP application and
    support of object services are important.
    For more information, see Business Context Facilities and Generic Object
    Relationships  (Extern).
    Business Applications
    MM
    The following documents relating to purchasing in MM can be stored:
      Outgoing purchasing documents
      Requests for quotation
      Purchase orders
      Scheduling agreements
      Forecast delivery schedules
      Contracts
    SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
    SAP ArchiveLink: Overview
    14 April 2001
      Incoming purchasing documents
      Quotations
      Order confirmations
      Incoming invoices and credit memos
      Incoming delivery notes
      Print lists
    For more information about storing in MM, see SAP ArchiveLink - Storage Scenarios in MM
    (Seite 74).
    SD/WS
    The following are examples of sales documents that can be stored:
      Incoming customer inquiries and customer inquiry changes
      Outgoing customer quotations
      Incoming purchase orders and purchase order changes
      Outgoing order confirmations
    For more information about storing in SD, see SAP ArchiveLink - Storage Scenarios in SD [Seite
    50].
    PA
    The following personnel administration and payroll documents can be stored:
      Incoming HR master data documents
      Incoming recruitment documents
      Incoming travel management documents
    For more information about storing in PA, see SAP ArchiveLink - Storage Scenarios in PA [Seite
    204].
    QM
    The following QM documents can be stored:
      Incoming documents for quality notifications (for example, customer complaints)
      Outgoing documents for quality notifications (for example, letter of complaint to vendor)
      Outgoing quality certificates
    For more information about storing in QM, see SAP ArchiveLink - Storage Scenarios in QM
    (Seite 93).
    The DMS and Applications Connected with the DMS
    In the DMS and in applications that are connected with the DMS (often MM and PP), the
    following documents can be stored:
      Incoming documents
      Originals managed in the DMS (PC files)
    SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
    SAP ArchiveLink: Overview
    April 2001 15
    For more information about storing in the DMS, see Storing in Document Management (CADMS)
    (Seite 24).
    SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
    Customizing
    16 April 2001
    Customizing
    Customizing is divided into three areas:
      General Customizing for SAP ArchiveLink
      Customizing for SAP Business Workflow
      Application-specific Customizing for individual SAP ArchiveLink scenarios
    General Customizing for SAP ArchiveLink
    To make these settings, proceed as follows:
    Use the Implementation Guide (IMG):
    Basis   Basis Services   SAP ArchiveLink
    For further information, see the Customizing  (Extern) section in the documentation SAP
    ArchiveLink.
    Customizing for SAP Business Workflow
    For the storage scenarios that use SAP Business Workflow:
      Storing for Subsequent Entry  (Extern)
      Storing for Subsequent Assignment  (Extern)
      Storing and Entering  (Extern)
      Storing and Assigning  (Extern)
    you must make Workflow Customizing settings.
    For further information, see the section Specific Customizing  (Extern) in the documentation SAP
    ArchiveLink and the IMG (Basis   Basis Services   SAP ArchiveLink).
    Application-Specific Customizing
    In the individual application scenarios, further customizing settings are required. The
    application-specific customizing for each SAP application component is described in the following
    sections of this documentation.
    SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
    Aim of this Documentation
    April 2001 17
    Aim of this Documentation
    This documentation describes the SAP ArchiveLink scenarios that are delivered as part of the
    standard system by SAP. There is a section for each storage scenario. The documentation
    describes the standard software.
    Each storage scenario description is assigned to one of the “big” application components in the
    SAP System. Storage scenarios in the following application components are currently described:
      BC (Basis)
      CA (Cross-Application Components)
      FI (Financial Accounting)
      SD (Sales and Distribution)
      MM (Materials Management)
      IS-RE (Real Estate Management)
      QM (Quality Management)
      PP (Production Planning and Control)
      PM (Plant Maintenance and Service Management)
      PA (Human Resource Management)
      PY-DE (Payroll Germany)
    The individual storage scenarios are structured as function descriptions and generally contain the
    following sections:
    Section Description
    Use Business background
    (this section is sometimes separate from the pure function description).
    You learn which application scenarios SAP ArchiveLink supports, which
    employees are involved and the advantages and simplifications offered by SAP
    ArchiveLink.
    This information is enough to give you a first overview of the storage scenarios.
    SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
    Aim of this Documentation
    18 April 2001
    Prerequisites   Technical implementation
    You become familiar with the document types and the corresponding technical
    document classes that form the basis of the scenario. You discover which object
    types and link tables are used.
    This information is particularly useful if you are planning to enhance or change
    the scenario.
      Preparation and Customizing
    The settings that are necessary to adapt the scenario to the specific
    requirements of your corporate structure are described.
    The settings described are scenario-specific and usually complement the SAP
    application component Customizing.
    Activities This section describes the technical and business connection of the scenario to
    the R/3 application and how the corresponding application functions are called.
    This documentation is not intended to replace the SAP ArchiveLink
    documentation and should only be seen as a central reference point for
    documentation relating to the implementation of SAP ArchiveLink in the individual
    SAP applications.
    To find out more about using SAP ArchiveLink and make full use of the functions for
    enhancements and in-house developments, see the SAP ArchiveLink  (Extern)
    documentation.
    SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
    SAP ArchiveLink - Storage Scenarios (BC)
    April 2001 19
    SAP ArchiveLink - Storage Scenarios (BC)
    Ablegen von Listen mit SAP ArchiveLink  (Extern)
    The following sections describe storage scenarios in R/3 Basis (BC):
      Storing Lists in the Report Tree
      Storing Print Lists
      Storing SAPoffice Documents
    See also:
      General Introduction  (Seite 10) to this scenario documentation
      SAP ArchiveLink  (Extern) documentation
      General Report Selection  (Extern) documentation
      BC - ABAP Programming  (Extern) documentation
    SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
    Storing Lists in the Report Tree (BC)
    20 April 2001
    Storing Lists in the Report Tree (BC)
    Use
    This section describes the storing of lists generated by executing reports in report trees. The
    process is not application-specific and is usually possible for any list unless storing is specifically
    prohibited in the program.
    Users can access reports that they require in the hierarchical structure of the report tree easily
    from all applications, via general report selection in the SAP information system.
    The SAP standard report tree contains several standard reports for all applications. To access
    reports from a particular application, you must expand the structure until you reach a list of
    reports on the lowest level. Here you select and execute the required report. You can display the
    result on the screen or print it via the spool system.
    Companies can configure the standard report tree to suit their requirements. For example, you
    can add your own reports or pre-generated lists and even change the entire structure.
    Prerequisites
    Technical Implementation (BC)
    Object type
    SREPOTREE
    Document type
    ABAP
    Link table
    TOA01
    For further information on executing reports and displaying pre-generated lists in report trees,
    see General Report Selection  (Extern).
    Technical Implementation (BC)
    Although storing lists generated in the report tree is similar for all applications, the report tree
    available to you may vary from the SAP standard, since your company can adjust the SAP
    standard report tree to suit its requirements.
    For further information on Customizing the report tree, see the Implementation Guide (IMG).
    Choose
    Tools   Business Engineer   Customizing
    Implementation projects   Display SAP Reference IMG
    and then Basis   Reporting - Report tree.
    Activities
    Storing lists
    When you have executed a report in the report tree, you can save the result list there and store it
    simultaneously.
    SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
    Storing Lists in the Report Tree (BC)
    April 2001 21
    To save your list and store at the same time:
    1. Choose System   List   Save   Report tree.
    2. Select Store in the dialog box displayed and specify where the list should be stored in the
    report tree. Specify the values for Report tree and Nodes.
    3. Choose Save.
    You have now saved your list in the report tree and the process is complete.
    Displaying information on storing lists
    You can check whether a list has been stored in the report tree:
    To check whether a list has been stored:
    1. Position the cursor on the relevant list.
    2. Choose Utilities   List information.
    The System displays a dialog box. The check boxes indicate whether the list has been
    stored.
    Displaying stored lists
    To display a stored list in the report tree, choose the relevant list by double-clicking.
    SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
    Storing Business Workplace Documents
    22 April 2001
    Storing Business Workplace Documents
    Use
    Documents stored in the Business Workplace  (Extern) are usually stored in the R/3 database (PC
    documents and binary documents can also be stored in an HTTP content server). To save
    memory space in the database, you can store documents in an external storage system using
    SAP ArchiveLink. The content of the documents that you have stored using SAP ArchiveLink is
    then deleted from the database.
    You can only retrieve Workplace documents stored using SAP ArchiveLink from the
    external storage system, from within the R/3 System. Direct access within the
    storage system is not possible.
    Prerequisites
    Technical Implementation
    Object type
    SOFM
    Link table
    TOA01
    Document class
    BIN
    Document type
    SOAARCHIVE Description: Office data object
    Preparation and Customizing
    To store documents from the Business Workplace, a content server must be maintained for the
    object type SOFM and the object class SOAARCHIVE in Customizing  (Extern) for SAP
    ArchiveLink.
    To perform mass archiving of Workplace documents, you need authorization  (Extern) for
    Workplace administration. This authorization is contained in the role SAP_BPT_USER.
    Activities
    Proceed as described in Mass Archiving  (Extern).
    The procedure for displaying and changing documents stored in the archive is no different for the
    user than the procedure for documents stored in the R/3 database. Calling documents from the
    archive usually takes longer, however.
    SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
    SAP ArchiveLink - Storage Scenarios (CA)
    April 2001 23
    SAP ArchiveLink - Storage Scenarios (CA)
    The following sections describe the storage scenarios in the R/3 application component CA
    (Cross-Application):
      Document Management System (CA-DMS)
      Data Achiving (CA-ARC)
    See also:
      General Introduction  (Seite 10) to the scenario documentation
      SAP ArchiveLink  (Extern)
      Application Data Archiving  (Extern)
      Document Management System  (Extern)
    SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
    Optical Archiving in Document Management (CA-DMS)
    24 April 2001
    Optical Archiving in Document Management (CA-DMS)
    eingehende Dokumente  (Seite 30)
    You can use SAP ArchiveLink® to archive documents from the document management system
    (DMS) in optical archiving systems.
    Documents Input when Processed (CA-DMS)  (Seite 30)
    Checking a Document into an Archive (CA-DMS)  (Seite 31)
    Displaying an Archived Document (CA-DMS)  (Seite 32)
    Copying an Archived Document to a Document Info Record (CA-DMS)  (Seite 33)
    Digital Original Application Files (CA-DMS)  (Seite 25)
    Archiving an Original Application File (CA-DMS)  (Seite 26)
    Creating a New Version (CA-DMS)  (Seite 27)
    Changing an Original Application File for an Existing Version (CA-DMS)  (Seite 28)
    Displaying an Archived Original Application File (CA-DMS)  (Seite 29)
    SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
    Digital Original Application Files (CA-DMS)
    April 2001 25
    Digital Original Application Files (CA-DMS)
    For each document info record, you can maintain and archive two original application files.
    Each original application file can be linked to a maximum of 99 additional files. These are
    archived automatically when you archive the original application file.
    Functions
    You process original application files with the following menu option of the document info record:
    Extras   Originals   File 1(2)
    The following functions for archiving and processing archived original application files are
    available:
      Archiving an Original Application File (CA-DMS)  (Seite 26)
      Creating a New Version (CA-DMS)  (Seite 27)
      Changing an Original Application File for an Existing Version (CA-DMS)  (Seite 28)
      Displaying an Archived Original Application File (CA-DMS)  (Seite 29)
    Notes on archiving original application files
      The system checks the application that is used to process the original application file (for
    example, WinWord 7.0).
    In the IMG for the Document Management System in the activity Define workstation
    applications, you define the archives for the various applications (for example, archive A2
    for the application WinWord 7.0).
      The system does not log the archiving of original application files. However, in the IMG for
    the Document Management System, you can define in the activity Define document types
    that all field changes are to be logged (Indicator: Create change documents).
    If you have archived an original application file with the function Check in archive, you
    can track any changes to the storage data (fields Data carrier and Original) in the change
    documents.
    Notes on processing archived original application files
    You have two options for processing an archived original application file:
      Creating a New Version (CA-DMS)  (Seite 27)
      Changing an Original Application File for an Existing Version (CA-DMS)  (Seite 28)
    See also:
    Figure: Changing an Archived Original Application File  (Extern)
    SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
    Archiving an Original Application File (CA-DMS)
    26 April 2001
    Archiving an Original Application File (CA-DMS)
    You archive an original application file if you want to save the current processing status for
    documentation purposes.
    See also:
    Figure: Archiving Original Application Files  (Extern)
    To archive an original application file:
    1. Process the document in change mode (Basic data screen).
    2. Choose Extras   Originals   File 1(2)   Check in archive.
    The system saves the original application file to the optical disk defined in Customizing.
    You see a dialog box with the following message:
    Document archived successfully
    3. You can check which archive the document was saved to.
    To do this, display the data carrier and path for the original application data by choosing
    Storage data.
    The data carrier and the path where the original application file was stored before being
    checked in the archive is no longer displayed. The system has overwritten this data with
    the archive data.
    If the document type is defined such that all field changes are logged, you can still
    display the previous storage place (Goto   Display changes).
    4. Save your document info record.
    SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
    Creating a New Version (CA-DMS)
    April 2001 27
    Creating a New Version (CA-DMS)
    This means that you keep the old version (for example, 00) containing the archived original
    application file and create a new version (for example, 01) directly from the old version. For the
    new version, you then change the original application file.
    To process the archived original application file (new version):
    1. On the Basic data screen, choose Document   New version.
    The system copies the data of the existing version (for example, 00), including the archived
    original application data.
    2. In the new version (for example, 01), the original application file is still archived.
    3. Choose Extras   File 1(2)   Change.
    The system automatically creates a copy of the checked in original application file.
    – Enter the target for the copy. This path identifies the place where the original
    application file for the new version (for example, 01) is stored.
    – If the system accepts your entries, you see a dialog box with the following message:
    Data copied from archive
    SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
    Changing an Original Application File for an Existing Version (CA-DMS)
    28 April 2001
    Changing an Original Application File for an Existing
    Version (CA-DMS)
    This means that you change the version whose original application file has been archived. There
    is only one version in this case.
    You can display the processing status that the original application file had in the archive from the
    status log if the following applies:
    When checking the original application file into the archive, you set a status for which the
    Indicator: Audit function is selected. This indicator causes original application files that are
    checked into the SAP database, a vault, or an archive with this status to be stored automatically.
    To change the archived original application file (existing version):
    1. Choose Extras   Originals   File 1(2)   Change.
    The system automatically creates a copy of the archived original application file.
    2. You see a dialog box, where you can enter the target for the copy. As a default value, you
    see the path where the file was stored before being archived.
    – To accept the default value, choose Continue.
    – If you want the file to be copied elsewhere, enter the required data (data carrier,
    path, and file name) in the dialog box. This path identifies the place where the
    original application file for the same version is stored. The system overwrites the
    previous archive data.
    If the system accepts your entries, you see a dialog box with the following message:
    Data copied from archive
    SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
    Displaying an Archived Original Application File (CA-DMS)
    April 2001 29
    Displaying an Archived Original Application File (CADMS)
    To display an original application file, you always use the following function, whether the data is
    stored on a server or in an archive:
    Extras   Originals   File 1 (2)   Display.
    The system automatically determines the path in the computer network. If the original application
    file is stored in an archive, you see a dialog box with the following message:
    Data copied from archive
    You can display archived data only from computers that have SAP ArchiveLink
    software installed.
    SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
    Documents Input when Processed (CA-DMS)
    30 April 2001
    Documents Input when Processed (CA-DMS)
    You process documents input when processed in the Archive menu of the document info record.
    The following functions are available:
    Checking a Document into an Archive (CA-DMS)  (Seite 31)
    Displaying an Archived Document (CA-DMS)  (Seite 32)
    Copying an Archived Document to a Document Info Record (CA-DMS)  (Seite 33)
    SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
    Checking a Document into an Archive (CA-DMS)
    April 2001 31
    Checking a Document into an Archive (CA-DMS)
    You use this function to check a scanned-in document (image) into an optical archive.
    See also:
    Scenario: Checking a Document into an Archive  (Extern)
    To check a document into an archive:
    1. Two windows are active on your computer screen:
    – a scan window with a scanned-in document
    – a window for the R/3 document management system
    2. In the document management window, choose the function you require (Document 
    Create or Change).
    Enter the required data on the initial screen and choose ENTER. You see the Basic data
    screen.
    3. Choose Archive   Check into archive.
    The system checks whether a status network that supports a status of status type A
    (archived) is defined for the chosen document type.
    Archiving is possible in the following cases:
    – if the status network does not support a status of status type A
    – if the status network supports a status of status type A at the current processing
    stage.
    The system automatically sets the status of status type A and records the status
    change in the status log.
    The system automatically determines the archive that is defined in the IMG
    functionOptical Archive.
    When the data has been archived, you see a dialog box with the following message:
    Document archived successfully
    4. Save your document info record.
    SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
    Displaying an Archived Document (CA-DMS)
    32 April 2001
    Displaying an Archived Document (CA-DMS)
    You use this function you to display documents that were either scanned in when processed,
    then archived, or copied from the archive from the document info record.
    This function is only active it at least one document has been archived for the chosen
    document info record.
    To display a document from the archive:
    1. Choose menu option Archive   Display from archive.
    2. What you do next depends on the situation:
      If only one archived document exists for the document info record, the system goes
    directly to the display program (viewer) and displays the document.
      If more than one archived documents exist for the document info record, you first
    see a dialog box listing the archived objects with the date on which they were
    archived.
      On the list, select the archived objects you want to display in the viewer.
      Choose the Choose pushbutton.
    The system goes to the first selected object.
    In the viewer, you can switch between the objects you selected by choosing the
    appropriate function (Object + or Object -) from the Goto menu.
    3. To exit the display function for archived objects, close the viewer with Document   Exit.
    You can now continue processing the document info record.
    SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
    Copying an Archived Document to a Document Info Record (CA-DMS)
    April 2001 33
    Copying an Archived Document to a Document Info
    Record (CA-DMS)
    This function allows you to copy a document that has been archived by another application (for
    example, SAPoffice) to a document info record.
    See also:
    Scenario: Copying an Archived Document to a Document Info Record  (Extern)
    Figure: Copying an Archived Document to a Document Info Record  (Extern)
    To copy a document from an archive:
    1. Two windows are active on your screen:
    – a window showing the document in the display program (viewer) of the archive
    – a window for the R/3 document management system
    2. In the document management window, choose the function you require (Document 
    Create or Change).
    3. Place the cursor on the viewer window again.
    – Choose Edit   Select
    This selects the scanned-in document for processing in the document management
    system.
    4. Place the cursor on the document management window.
    Choose Archive   Copy from archive.
    The system makes the same status checks as described in Checking a Document into
    an Archive (CA-DMS)  (Seite 31).
    SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
    SAP ArchiveLink and Application Data Archiving (CA-ARC)
    34 April 2001
    SAP ArchiveLink and Application Data Archiving (CAARC)
    Use
    You can use the Archive Development Kit data archiving transaction and SAP ArchiveLink to
    store archive files in external archives. For more information see: Technical Background (CAARC)
    (Extern).
    Prerequisites
    You must enter the following settings in customizing in order to use the SAP ArchiveLink
    interface to archive application data:
      Platform-independent filename
      Document type
      Automatic transfer of archive files
    Activities
      Checking Storage Status of Archive Files (CA-ARC)  (Seite 38)
      Storing Archive Files Manually (CA-ARC)  (Seite 39)
    See also:
    Setting Platform-independent Filenames for SAP ArchiveLink (CA-ARC)  (Seite 35)
    Setting Archive File Document Type (CA-ARC)  (Seite 36)
    Storing Archive Files Automatically (CA-ARC)  (Seite 37)
    SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
    Setting Platform-independent Filenames (CA-ARC)
    April 2001 35
    Setting Platform-independent Filenames (CA-ARC)
    1. Call the Archive Management.
    2. Enter the name of the archiving object and press Enter.
    3. Choose the Customizing function.
    4. In archiving object-specific customizing choose Technical Settings.
    5. In the logical filename field enter a filename that refers to the exchange directory of the
    attached SAP ArchiveLink archive system. For example, the logical filename
    ARCHIVE_DATA_FILE_WITH_ARCHIVE_LINK. The system delivers the following standard
    defined filename:
    , if you use this runtime variable in the specification of the
    physical path. For example, the physical path could be:
    ARCHIVE_GLOBAL_PATH_WITH_ARCHIVE_LINK. See the FILE transaction
    documentation for further information.
    See also:
      Setting Archive File Document Type (CA-ARC)  (Seite 36)
      Storing Completed Archive Files in the Archive System Automatically (CA-ARC)  (Seite 37)
    SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
    Setting Archive File Document Type (CA-ARC)
    36 April 2001
    Setting Archive File Document Type (CA-ARC)
    1. Call the Archive Management.
    2. Enter the name of the archiving object and press Enter.
    3. Choose the Customizing function.
    4. Choose Technical Settings in archiving object-specific customizing.
    5. Choose the document type Archive in the group box Archive System Link.
    See also:
      Setting Platform-independent Filenames for SAP ArchiveLink (CA-ARC)  (Seite 35)
      Storing Completed Archive Files in the Archive System Automatically (CA-ARC)  (Seite 37)
    SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
    Storing Completed Archive Files in the Archive System Automatically (CA-ARC)
    April 2001 37
    Storing Completed Archive Files in the Archive System
    Automatically (CA-ARC)
    1. Call the Archive Management.
    2. Enter the name of the archiving object and press Enter.
    3. Choose the Customizing function.
    4. Choose Technical Settings in archiving object-specific customizing.
    5. Mark the checkbox Exec. automat. in the group box Archive System Link.
    See also:
      Setting Platform-independent Filenames (CA-ARC)  (Seite 35)
      Setting Archive File Document Type (CA-ARC)  (Seite 36)
    SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
    Determining Whether an Archive File is Stored in the Optical Archive (CA-ARC)
    38 April 2001
    Determining Whether an Archive File is Stored in the
    Optical Archive (CA-ARC)
    1. Call the Archive Management.
    2. Enter the name of the archiving object and press Enter.
    3. Choose the Management function.
    4. Set the cursor on the file whose archive residence you want to know, and double-click.
    The Archive Management: Archiving File Detail popup appears. Read the Storage option
    status text.
    See also:
    Storing Completed Archive Files in the Archive System Manually (CA-ARC)  (Seite 39)
    SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
    Storing Completed Archive Files in the Archive System Manually (CA-ARC)
    April 2001 39
    Storing Completed Archive Files in the Archive System
    Manually (CA-ARC)
    Only archive files whose data objects have been deleted in the database can be
    stored in an external archive system.
    1. Call the Archive Management.
    2. Enter the name of the archiving object and press Enter.
    3. Choose the Management function.
    4. Set the cursor on the file which you want to store in the external archive system.
    If you want to store all the files in a session, set the cursor on the session number.
    5. Choose the Store function.
    The Archive Management: Store via ArchiveLink popup appears.
    6. Choose the Store Files function.
    The file is passed to the external archive system.
    See also:
    Determining Whether an Archive File is Stored in the External Archive (CA-ARC)  (Seite 38)
    SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
    SAP ArchiveLink - Storage Scenarios (FI)
    40 April 2001
    SAP ArchiveLink - Storage Scenarios (FI)
    The following sections describe storage scenarios in the Financial Accounting (FI) application
    component.
    See also
      The general introduction  (Seite 10) to this scenario documentation
      SAP ArchiveLink  (Extern)dokumentation
      Financial Accounting documentation
    SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
    Storing Print Lists (FI)
    April 2001 41
    Storing Print Lists (FI)
    Use
    In the FI application component, you can use SAP ArchiveLink to transfer the following print
    lists to an external storage system:
      Compact document journal (RFBELJ00)
      Line item journal (RFEPOJ00)
      Open item account balance audit trail (RFKKBU00)
      Accumulated account balance audit trail (RFKLBU10)
    Storage using SAP ArchiveLink has the following advantages:
      Reduced burden on online system
      Safer storage
      Faster, easier access
    Prerequisites
    Technical Realization (FI)
    Following improvements to the print reports, the print lists are now provided with an index when
    they are stored, enabling you to access objects (including sub-objects) at a later date.
    A particular account in the account balance audit trail.
    The system also generates a link to any stored documents that might exist, enabling you to
    display the corresponding stored document from the stored print list.
    For a detailed description of how to store print lists, refer to Print Lists  (Extern) in the SAP
    ArchiveLink documentation.
    There are no plans for enhancements.
    Preparation and Customizing (FI)
    No special Customizing settings are required to be able to store print lists in FI. For
    information on the Customizing settings for SAP ArchiveLink, see Customizing  (Seite 16).
    Special authorizations are not required.
    SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
    Storing Print Lists (FI)
    42 April 2001
    Activities
    For notes on using these functions (in particular displaying stored print lists) see
    Searching for, Displaying and Printing Print Lists  (Extern) in the SAP ArchiveLink
    documentation.
    To store print lists in the FI application component, proceed as follows:
    1. Run the appropriate program and enter your selection criteria.
    2. On the selection screen, choose Optical archiving and enter the following information in
    the dialog box that is now displayed:
    – Object class: DRAW (document)
    – Object type: D01 (print list)
    – Identification: XXX (three figure alphanumeric code of your choice)
    – Text: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX (up to 30 characters
    long).
    3. Now choose Execute in background or Execute + Print.
    To view the stored list, from the R/3 System initial screen, choose
    Office   Business Documents   Find lists. Enter the name of the report program and
    any additional selection criteria. Choose Enter. From the list that is now displayed you
    can select a print list and display its contents.
    When displaying the list, you can also display the incoming and outgoing documents
    (provided these were also stored). You do this via hyperlinks which are recognizable
    as such by being underlined.
    SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
    Storing Incoming Documents (FI)
    April 2001 43
    Storing Incoming Documents (FI)
    Use
    In the FI application component, you can transfer incoming documents (invoices, credit memos)
    to an external archive system using SAP ArchiveLink. Data can be stored in different ways:
      Store for subsequent entry
      Store and enter, and
      Late storing with bar codes
      Assign, then store
    For detailed information on the ways in which you can store documents, see Storage
    Strategies  (Extern) in the SAP ArchiveLink documentation.
    The procedure Store for entry later with document parking is different to other storage
    methods. Under this procedure, processing is even more automated than it would otherwise be.
    The accounting clerk responsible for parking documents receives an incoming document (an
    invoice for example) via SAP Business Workflow. In the entry transaction to which the invoice
    is subject, the clerk can park this document using the existing incoming document. He or she can
    then send the parked invoice together with the incoming document for further processing
    (approval or additional investigation) to the relevant colleague. This colleague can then complete
    processing and post the invoice.
    Prerequisites
    Technical Realization (FI)
    Object type
    BKPF (financial accounting document)
    Link table
    TOA01
    Document class
    FAX
    Document type
    In the standard system, the following document types are supplied for the R/3 FI application
    component.
    FI document Document type
    Incoming invoice without invoice verification FIIINVOICE
    Incoming credit memos without invoice verification FICREDIT
    Incoming invoice parking FIIINVPREL
    SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
    Storing Incoming Documents (FI)
    44 April 2001
    Fast invoice entry FIIPAYMEN2
    Incoming payment FIIPAYMENT
    Enhancements
      You can define your own document types under
    Tools   Business Documents
      Document types   Global document types and
    Tools   Business Documents
      Document types   WFL document types.
      You can define your own transaction links under
    Tools   Business Documents
    Document types   Workflow parameters.
    Further information
    For basic technical information on adding SAP ArchiveLink functions to the R/3 application
    components, refer to the section Incoming Documents  (Extern) in the SAP ArchiveLink
    documentation.
    Preparation and Customizing (FI)
    The basic preliminary settings that you must make in SAP ArchiveLink are described in
    Customizing  (Seite 16)
    You need to make settings in Customizing for Financial Accounting only for the activity Late
    storing with bar codes. For more information, see the documentation for the activities Specify
    Control Parameters for Bar Code Entry and Maintain Document Types for Bar Code Entry
    located in Customizing for Financial Accounting under Financial Accounting Global Settings 
    Document   Document Header.
    Activities
    Scenario: Assignment and Storage in FI
    For information on this procedure, see the following sections of the SAP ArchiveLink
    documentation:
    Scenario: Late Storage with Bar Codes in FI
    For information on this topic, see:
      Process: Late Storing with Bar Codes  (Extern)
      Concept: Storing with Bar Codes  (Extern)
    SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
    Storing Incoming Documents (FI)
    April 2001 45
    Scenario: Store for Subsequent Entry in FI
    For information on this topic, see:
      Concept: Store for Subsequent Entry  (Extern)
      Process: Store for Subsequent Entry  (Extern)
      Store for Subsequent Entry  (Extern)
    Scenario: Entry and Storage in FI
    For information on this topic, see:
      Concept: Store and Enter  (Extern)
      Process: Store and Enter  (Extern)
      Store and Enter  (Extern)
    Document Processing Functions
    In certain document processing transactions in FI you have direct access to the functions
    available under SAP ArchiveLink. These transactions include:
      Changing documents (FB02)
      Displaying documents (FB03)
      Changing parked documents (FBV2)
      Displaying parked documents (FBV3)
    When carrying out these transactions, you can use the following functions:
      Subsequently assign a stored document from the external content server (see Assign
    Stored Documents Subsequently  (Extern))
      Display the stored document for an FI document from the external content server (see
    Searching for Incoming Documents  (Extern))
    The assignment and display functions might typically be accessed as follows:
    1. From the General Ledger menu, choose Document   Display.
    2. Enter the document number and the company code in which it was posted. Choose
    ENTER.
    The system now displays the R/3 document.
    3. To display the stored document for this R/3 document, choose Environment   Object
    links
    To assign this document to a document already stored, choose Environment   Assign
    original.
    SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
    Storing Incoming Documents (FI)
    46 April 2001
    SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
    Storing Outgoing Documents (FI)
    April 2001 47
    Storing Outgoing Documents (FI)
    Use
    You can store documents transferred from the General Ledger (FI-GL), Accounts Receivable (FIAR)
    and Accounts Payable (FI-AP) application components using SAP ArchiveLink. Documents
    that you created using SAPscript are stored in an external storage system and linked to the
    documents or accounts from which they are derived. You can store the following outgoing
    financial accounting documents:
      Payment advice notes
      Checks
      Correspondence like payment notifications and bank statements
      Dunning notices
    Storage using SAP ArchiveLink takes place using Business Transaction Events, to which end
    SAP supplies sample function modules that you can activate by making the appropriate
    Customizing settings.
    If you already use your own programs (user exits) or Business Transaction Events to
    manage printing, faxing, email or dispatching, check whether you need to replace
    these developments with a function module enhanced to perform these functions.
    IMPORTANT: Ensure that no data is overwritten.
    Prerequisites
    Technical Realization (FI)
    Object type
    BKPF (financial accounting document)
    BUS3007 (customer account)
    BUS3008 (vendor account)
    Link table
    TOA01
    Document class
    PDF
    Document type
    The following document types exist in the standard system:
    FI document Document type Function module
    Payment advice note FIOPAYAVIS FI_OPT_ARCHIVE_PAYMENT_ADVICE
    SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
    Storing Outgoing Documents (FI)
    48 April 2001
    Check FIOPAYMENT FI_OPT_ARCHIVE_ PAYMENT
    Correspondence:
    Payment notification
    Bank statement
    FIOPAYCONF
    FIOACCSTAT
    FI_OPT_ARCHIVE_CORRESPONDENCE
    Dunning notice FIODUNNING FI_OPT_ARCHIVE_DUNNING_NOTICE
    If you make changes in Customizing to the object types and document types, you will need to
    adapt the corresponding function modules in each case.
    Enhancements
    There are no restrictions to the way in which sample function modules in the standard system
    can be enhanced. They can also be duplicated for additional document types and object types as
    many times as necessary.
      You can define your own document types in the Basis Implementation Guide under
    Basis Services   SAP ArchiveLink   System Settings   Maintain Document Types.
      To define you our own object types, on the SAP R/3 screen, choose
    Tools   Business Framework   BAPI development   Business Object Builder.
      The sample function module FI_OPT_ARCHIVE_CORRESPONDENCE contains the
    correspondence types SAP01 (payment notificiation) and SAP08 (account statement).
    Additional correspondence types can be added to this function module. You can define
    correspondence types in Customizing for Financial Accounting under the
    Implementation Guide under
    Financial Accounting Global Settings   Correspondence   Define Correspondence
    Types.
    Preparation and Customizing (FI)
    To activate storage for financial accounting documents using SAP ArchiveLink, make the
    following settings in Customizing:
    1. If you want to make changes to the function modules (changing the document type
    defined in the standard system for example) copy the sample function modules to your
    name range. You should then make these changes in the source text.
    For a detailed description of the procedure for copying sample function modules to your
    name range, see the IMG documentation for the activity Use Business Transaction
    Events (located under Financial Accounting Global Settings.)
    2. Define the storage method in the function modules. Enter the setting in source text for
    the parameter c_itcpo-tdarmod. The following settings are possible:
      2 Store only
      3 Print and store
    3. Create a product with which all function modules that you want to activate can be
    summarized at a later date.
    To do this, choose the activity Use Business Transaction Events, located in Customizing
    for Financial Accounting under Financial Accounting Global Settings. On the SAP
    SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
    Storing Outgoing Documents (FI)
    April 2001 49
    Business Framework: Business Transaction Events screen, choose Settings   Products
      ... of a customer. Mark this product as active by selecting the Active indicator.
    4. Assign the function modules to processes (Events).
    To do this, choose the activity Use Business Transaction Events, located in Customizing
    for Financial Accounting under Financial Accounting Global Settings. On the Business
    Framework: Business Transaction Events screen, choose Settings   P/S function
    modules   ... of a customer. In the table that is now displayed, enter the names of the
    function modules that you want to activate, together with the Events or products required.
    Enter also the name of the product already created.
    The names of the processes defined in the standard system are as follows:
    Function module Process
    FI_OPT_ARCHIVE_PAYMENT_ADVICE 00002050
    FI_OPT_ARCHIVE_ PAYMENT 00002060
    FI_OPT_ARCHIVE_CORRESPONDENCE 00002310
    FI_OPT_ARCHIVE_DUNNING_NOTICE 00001040
    Activities
    Storing outgoing documents (FI)
    Outgoing documents are stored automatically if you have carried out the above-mentioned
    settings in Customizing.
    Displaying stored documents
    Stored documents can be displayed as follows:
      On the SAP R/3 screen, by choosing Office   Business Documents   Documents 
    Find lists
      From the Accounts Receivable or Accounts Payable menu by choosing Master records
      Display.
    Enter the customer or vendor you wish to display, select one of the indicators under
    Company code data and choose ENTER.
    On the screen that is now displayed, choose System   Display relationships   Stored
    documents.
    SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
    SAP ArchiveLink - Archiving Scenarios (SD)
    50 April 2001
    SAP ArchiveLink - Archiving Scenarios (SD)
    The following sections describe the archiving scenarios in the R/3 application component SD
    (Sales and Distribution):
      General sales and distribution (SD)
      Sales support (SD-CAS)
    See also
      General Introduction  (Seite 10) to this scenario documentation
      SAP ArchiveLink  (Extern)documentation
      Sales and distribution  (Extern) documentation
      Sales support  (Extern) documentation
    SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
    Optical Archiving of Incoming Original Documents (SD)
    April 2001 51
    Optical Archiving of Incoming Original Documents (SD)
    Betriebswirtschaftlicher Hintergrund (SD)  (Seite 52)
    Weitere Voreinstellungen  (Extern)
    Spezial-Customizing  (Extern)
    Ablegen für spätere Erfassung  (Extern)
    Zuordnen und Ablegen  (Extern)
    Spät ablegen mit Barcode  (Extern)
    Ablegen und Erfassen  (Extern)
    SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
    Business Background (SD)
    52 April 2001
    Business Background (SD)
    The Sales and Distribution application component contains an SAP ArchiveLink function that
    provides sales personnel with a quick and efficient means of optically archiving and processing a
    wide range of incoming documents including inquiries, purchase orders, contracts, and
    complaints. SAP ArchiveLink offers easy online access to these archived documents during the
    planning, processing, and analyzing of business transactions in Sales and Distribution.
    The SAP ArchiveLink interface supports the following archiving scenarios for incoming
    documents in SD:
      Early archiving
      Late archiving
      Late archiving using bar codes
      Simultaneous archiving
    Early Archiving
    In the early archiving scenario, incoming paper documents are archived in the R/3 System before
    an SD document is created.
    In early archiving, the archiving process usually begins in a central mailroom where a designated
    person opens, presorts, prepares, and records (scans) the incoming mail. Once an incoming
    document is scanned and an incoming document type is assigned to it, the system triggers the
    SAP Business Workflow to notify the authorized employee(s) that an incoming document has
    been received and is due to be processed. When the employee accesses the archived
    document, the system automatically calls up the relevant business transaction, such as Create
    sales order, according to the incoming document type. After the employee creates and saves the
    SD document, the system automatically assigns the archived document to it.
    For a detailed description of early archiving, see Early Archiving (SD)  (Seite 54).
    Late Archiving
    In the late archiving scenario, incoming paper documents are archived in the R/3 System and
    assigned to existing Sales and Distribution documents.
    In late archiving, an employee processes an original document directly from paper or carries out
    a sales activity before receiving an original document. At a later point in time, the original
    document is scanned into the system and archived as a facsimile. It is then assigned to the
    existing SD document by:
      The person at the archiving station who scans the original documents
      The person responsible for processing the SD document
    As in the scenario for early archiving, the archiving process usually takes place in a central
    location at the company.
    For a detailed description of late archiving, see Late Archiving (SD)  (Seite 55).
    Late Archiving Using Bar Codes
    Late archiving using bar codes is a special form of late archiving. In this case, however, a bar
    code is attached to the incoming document either in the mail room or at the time of processing.
    SAP AG SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL)
    Business Background (SD)
    April 2001 53
    An SD document is created from the original document whose bar code ID is linked to the SD
    document number. Later, the original document is scanned into the system which recognizes the
    bar code ID and automatically makes the proper assignment to the SD document.
    For a detailed description of late archiving using bar codes, see Late Archiving Using Bar Codes
    (SD)  (Seite 56).
    Simultaneous Archiving
    Simultaneous archiving is a special form of early archiving in which the incoming document is
    scanned into the system, optically archived and, at the same time in another window, the
    corresponding SD document is created or changed. The system does not activate SAP
    Business Workflow in this case; no mail is sent.
    For a detailed description of simultaneous archiving, see Simultaneous Archiving (SD)  (Seite 57).
    SAP ArchiveLink - Scenarios in Applications (BC-SRV-ARL) SAP AG
    Early Archiving (SD)
    54 April 2001
    Early Archiving (SD)
    The following steps describe a typical scenario in which incoming paper documents are archived
    before a Sales and Distribution document is created:
    1. A clerk in the central mail room of a company receives a letter from a customer who wishes
    to buy several products.
    2. The clerk scans the letter into a scanning system.
    The system displays the letter in the scan dialog window.
    3. Using the SAP ArchiveLink interface in the R/3 System, the clerk or another designated
    employee selects the function for early archiving and chooses an appropriate incoming
    document type for the scanned document, for example, the general description “Customer
    response to a sales activity”, SDIACTRESP.
    4. The clerk confirms the assignment of the incoming document type.
    This triggers a workflow in which a mail is sent to the employee who is responsible for
    creating sales documents, in this case Mr. Jones in the Sales department.
    All employees who are to be notified by SAP Business Workflow must first be listed
    in the company’s organizational structure (see Customizing for SAP Business
    Workflow).
    5. Mr. Jones receives the work item in his integrated inbox. When he calls up the work item for
    processing, a dialog box appears in which Mr. Jones can confirm or overwrite th

Maybe you are looking for

  • Retrieving ServerHost and ServerPort in Server with Web Dispatcher

    Hi, I am using IWDRequest to get server host and port in my Web Dynpro DC. This is the code which I am using for it. IWDRequest req = WDProtocolAdapter.getProtocolAdapter().getRequestObject(); String l_str_host = req.getServerName(); int l_int_port =

  • How to compare 2 anagrams

    Hey everyone agian with another program the code i have so far how do i go about Comparing two items. initially i thought sort the characters in order from lowest alpha character to greatest then compare the two words, but i couldnt find a way to do

  • Shift Register and waiting time functions - DAQmx

    Thanks that worked. 

  • How to Uninstall the Trial Version of CS4 InDesign, clean?

    I need to get back to CS2 InDesign and I don't want to have any issues with my other Adobe products in the meantime, until I purchase the upgrade to CS4 later. I know that I use the installer program. But do I check the 'Remove Application Preference

  • Adobe CS2 NEF converter

    I have CS3 and a friend of mine has CS2. When she opens a RAW file in bridge the file opens CS2. Then she gets a error that this is not the right file. Can she use 4.4 RAW and if so where would she place it?