Delete Rate routing with archiving

Hi to all,
I want delete a rate routing with TC: CA99.
can any one help me, how to do that correctly?
tks in advance.
Rgds
Alaaeddine.

Hello BDH,
Go to CA99 screen, select the write action,
Create the variant (select the maintain)
Please insert required detail in field and save the variant.
Make sure deletion flag tab checked and test run tab unchecked
now execute this transction(if required take help from technical team for execution of this)
I hope this information helpful to you,,
Thanks & Regards
Umesh Mali

Similar Messages

  • Delete rate routing particular operation

    Dear all,
    In rate routing i need to need delete only operation 10 & 40 for this how handle this transaction in SAP.
    Example:
    10     Dummy
    20     Operation
    30     Operation
    40     Dummy
    Advance thanka
    By
    jack

    Dear
    There is no SAP Standrad Txn to mass delete operation in Rate rouning or any  type of routing .Even there is no FM or BAPI available for change routing. in mass but  you have BAPI for routing display and create
    The best option will be discuss with your  ABAPER  to develop a RFC enabled FM (called as RFC in Technical language)  and ask him to include BDC code for change operation/delete operation and all other thinghs which you want your BAPI should
    want you to perform .
    Hope this helps
    Regards
    JH

  • Delete split valuation with archiving process

    Hi,
    i have nice question about archiving.
    i have flagged for deletion my article at valuation level, i have checked if the are
    u2022     Use in routing
    u2022     Use in sales and distribution
    u2022     Use in bill of material
    u2022     Delivery exists
    u2022     Costing data exists
    u2022     Info record exists
    u2022     Purchase order exists
    as written in other answer that i find in the forum.
    so after this check i creat my archiving variant and i execute  it (no test) and it gaves me no error!
    it says:
    " MBEW   1  Material Valuation"
    "MBEW: 2000 Z2M2-DP-E4 material master record was archived"
    But if i goes in MM02 MM03 i can still see and change my article, i only received warning message for deletionflag.
    There is any body that can help me?
    i can i really check if the article is archived?
    thanks to all...

    you wrote an record to an archive, if that was not executed as test run.
    But writing an archive is just one step - next step is to run the deletion.
    In the deletion step SAP checks whether it can read the archive and if it can then the record from the R3 tables will be deleted.
    This step was probably not done yet.
    Execute SARA for MM_MATNR
    Click button DELETION
    Select your archive
    and schedule the job.

  • Material Deletion from Routing Groups-Mass T-code

    Dear Experts
    we have a big task we have to delete Routing assignments from Routing Groups we have around 4000 material codes.
    Is there any mass code to delete Material assignements from Routing group.
    Regards
    sandeep patil

    Hi,
    CWBQM from Mass change
    QSR6.
    Use transaction CA99 - delete task list with archiving, here enter PP_PLAN as the object name
    Also transaction CA98 can be used to delete w/o archiving
    BAPI_ROUTING_PROCESS
    Regards,
    R.Brahmankar

  • Transfer Master Data Rate Routing

    Hello Gurus,
    We need to transfer Master Data (Rate Routing) with ALE. We already configure the ALE connection. We need to know which is the Process Code in the Inbound Table.
    Anyone can help us, please.
    Thanks in advance.
    Best Regards.

    Check this link
    http://help.sap.com/saphelp_47x200/helpdata/en/92/58d455417011d189ec0000e81ddfac/frameset.htm
    For BOM and materials there are transaction codes...but i could not get for WC and Routing...

  • Reduction strategy in Rate routing.

    Hi
    I have a Rate routing with 3 WC for 3 operations
    Each operation take 30 mints to finsh
    If i want to produce 5 qty in the 3 WC.
    time taken for the machining is =  30 mins * 5 qty(WC1) +  30 mins * 5 qty(WC2)  + 30 mins * 5 qty(WC3)
                                                     =  71/2 HRS to finsh the 5qty jobs
    but as per normal -                            w1      w2      w3
                           JOBS          1       9:00 AM       9.30 am     10.00 am
                                             2       9.30 am     10.00 am     10.30 am
                                             3     10.00 am     10.30 am      11.00 am
                                             4     10.30 am      11.00 am     11.30 am
                                             5     11.00 am     11.30 am     12.00 am
    Total it will take 3 hrs to finish
    how to do this reduction in the Routing.
    what REDUCTION STRATEGY WE NEED TO USE . PLS EXPLAIN.
    Can i use the Contioud flow prod in the overlapping tab in the operation details
    Thanks
    vraj

    Hi,
    Yes, U can use Overlap strategy to meet your requirements. Please maintain all the values correctly and do some work around and test properly before doing it in production client.
    Regards
    Suri

  • Idoc ROUTING_CREATE01 and rate routing

    Hello,
    Is it possible to create rate routing with idoc ROUTING_CREATE01, so far I can create only simple routing.
    Thanks for your answer.

    Hi,
    For rate routing:
    use this BAPI: 'BAPI_ROUTING_CREATE' for creating Rate Routing
    Regards,
    Kumar(Reward if helpful).

  • Issue with Archiving & Deletion of messages in PI ,SXMB_MONI messages

    Hello experts
    I am  working on Archiving & Deletion of messages in PI ,SXMB_MONI, i have fallowed all the steps which are avialable in /people/deepak.shah/blog/2010/04/22/archiving-deletion-of-messages-in-pi--part-2, but the messages still there in SXMB_MONI.
    please help me to resolve this issue.
    regards
    chandra

    Hi Krish
    i have fallowed steps like....
    in SXMB_ADM
    >>>step 1: Define the interface for archivng and retnetion period
    >>>step2):Schedule Archive Jobs,
    after this i have checked the in SM37 the jobs got sheduled and released after that it showing finished.
    >>>step3):ARV_BC_XMB_WRP<date> (archiving, step 1)
    ARV_BC_XMB_DEL<date> (archiving, step 2)
    here i am getting message like "0 XML messages got archived".
    "0 XML message for deleated".
    I have doubt in SXMBPMAST  table here when i check the status of interface , ITFACTION field is containing the value INIT and if I understood correctly it job deletes only those messages where ITFACTION is set to DEL.
    We are actually trying to delete the messages avoiding archiving but what I am seeing is we cannot delete error messages and for them we must have to go through archiving. Please correct me if I am wrong.
    Thanks
    Chandra

  • Trying to delete a routing task list (N) and getting an error on CA98

    Getting an error when trying to delete a task list routing without archiving using t-code CA98. 
    Error:       "Task list 01184667 01 (type 01184667) is still used in inspection lots"
    The inspection lot is for a production order. The routing I am trying to delete was used in that production order.
    I found the inspection lot and there is a UD of accept on it but I cannot delete the task list routing.
    If I archived the task list routing for the material and tried to delete the task list routing would I still get the same error as above?
    Tom

    You can use CA98 only for test data which you no longer intend to use or refer to. I don't think even CA99(with archiving) can help here. Please check the dependencies for deletion of routings: [http://help.sap.com/saphelp_47x200/helpdata/en/7e/d41b73455911d189400000e8323c4f/content.htm]
    Thanks,
    Anil

  • How To Use Your Own Router with Out Loosing Verizon's FIOS Services

    How to use your own router with Verizon’s FIOS Service
    First, you need a basic understanding of how FIOS works but unfortunately there are two types of FIOS systems out there. All of the systems utilize a fiber optic cable to bring TV, phone and internet to your location over one optic cable. In addition these systems provide interactivity including widgets, remote DVR, movies on demand and so forth via an IP (Internet Protocol) signal.  Your STB (Set Tip Box) requires both a video and IP signal. The IP signal is necessary for all of the aforementioned interactivity.  The fiber cable terminates at the Optical Network Terminal or ONT for short.  The ONT converts the optics into a digital signal that can be utilized by ones equipment.  From the ONT your video, phone and internet are provided to the location.  This is where things can differ as the internet signal can be provided via a coaxial (MoCA or Multimedia over Coax Alliance) or RJ45 Cat5 (Ethernet) cable.  It is important to identify and understand the differences of these two setups.  In my case I have my internet entering via Ethernet cable, which in my humble opinion makes things a heck of a lot easier.
    How does one tell the difference? In most cases it’s rather simple; just look at the Verizon’s router WAN (Wide Area Network) Port.  Does it have a RJ45 (Ethernet) or Coax (TV cable Cord) going to it? If the router’s WAN port doesn’t have a coaxial connector then one will need to convert the MoCA signal into a usable Ethernet signal that routers understand. The easiest way is to use Verizon’s router as a bridge. In this method the Verizon’s router simply converts the signal and passes it along to your own router. The challenge is to try to maintain the interactivity that FIOS TV provides. Because of this one needs to supply the IP routed signal back to the FIOS router.  There are multiple methods for doing this and I would recommend investigates which one make the most sense.   
    In my particular case the IP signal was provided by Ethernet.  Again there are various ways of installing one’s own router. The hardest is to utilize Verizon’s router as a bridge.  This setup requires configuring Verizon’s router as a bridge and also creating a VLAN (Virtual Local Area Networks). In addition one needs to set up their own router so it will work with the various routing tables and networks. For me this is too complex for the average person and it can be difficult to trouble shoot if something goes wrong. Please consider that Verizon will not support utilizing third party routers.   
    The easier method is to request an Ethernet signal (if you don’t already have one) from their ONT.  I would highly recommend getting your hands on a NIM or Network Interface Module. This device is used to convert Ethernet to Coaxial so it can be fed back to your STBs.  These can be purchased online and Verizon technicians can be a valuable resource with these sorts of acquisition.  At the very least they can point you to the right direction.  Once you have a NIM the rest is rather simple.
    Log into the current Verizon Router.
    Located the router’s MAC address and copy it down.
    Go to the port forwarding section and copy down the Applied Rules. 
    Example:  
    Network Computer/Device: 192.168.1.100:63145
    Application & Ports Forward:  Application UDP Any -> 6347  
    Note: There may be up to three entries for each one of your Set Top Boxes.
    Look at your current device list, typically found on the home screen. Copy down your STB MAC and IP address.
    Example:
    IP-STB1
    Connection Type: Ethernet
    * IP Address: 192.168.1.100
    IP Address Allocation: DHCP
    *MAC Address:                07:73:fFe:ad:8b:3f
    * Things you will need to write down
    Go to the network section and look for the main Ethernet connection.  Select this and then select more setting, typically found at the bottom. Release the current lease.
    Remove the Verizon router
    Install your router
    Connect the NIM by plugging in an Ethernet from one of the routers LAN (Local Area Network) ports to your NIM. Then connect the coax cable, the same cable that was used by Verizon router.
    Set you DHCP routing IP pool to accommodate Verizon’s STB IP’s  (note their IP’s start at 192.168.1.100)
    Go to DHCP section and reserve the STB IP’s by inserting the IP’s and MAC addresses. This shall ensure that nothing else utilizes the same IPs as the STBs thereby preventing IP address conflict.  
    Add the port forwards from Step 5 above.
    Clone Verizon’s Mac Address utilizing the info from step 2
    Finish setting up the router in typical fashion.
    Unplug and re-plugin your STB’s and test functionality.  It’s best to try using a widget or Movie on demand function.
    Note: if the new router can net get an internet signal contact Verizon’s support and have them release the IP and reset the ONT.  
    EVERYTHING should be working at this point.

     3 Go to the port forwarding section and copy down the Applied Rules. 
    Example:  
    Network Computer/Device: 192.168.1.100:63145
    Application & Ports Forward:  Application UDP Any -> 6347  
    Note: There may be up to three entries for each one of your Set Top Boxes.G
    Your display obviously is not like mine as mine does not dosplay the port associated with the ip address
    whatever, the STB's start at 192.168.1.100 and icement by 1 for each
    the port addr's will be 63145 alo incrementing by 1
    there is 1 entry for each in my pf list
    however each ip addr also has a port entry starting at 35000 also incrementing by 1 for each ip addr
    For some unknow reason these are duplicated e.g I appear to have 11 entries exaactly the same for each stb and as the fios services rules have no action switc there is nowhere to delete the extraneous garbage.
    Why do you clone the mac addr??

  • RA VPN into ASA5505 behind C871 Router with one public IP address

    Hello,
    I have a network like below for testing remote access VPN to ASA5505 behind C871 router with one public IP address.
    PC1 (with VPN client)----Internet-----Modem----C871------ASA5505------PC2
    The  public IP address is assigned to the outside interface of the C871. The  C871 forwards incoming traffic UDP 500, 4500, and esp to the outside  interface of the ASA that has a private IP address. The PC1 can  establish a secure tunnel to the ASA. However, it is not able to ping or  access PC2. PC2 is also not able to ping PC1. The PC1 encrypts packets  to PC2 but the ASA does not to PC1. Maybe a NAT problem? I understand  removing C871 and just use ASA makes VPN much simpler and easier, but I  like to understand why it is not working with the current setup and  learn how to troubleshoot and fix it. Here's the running config for the C871 and ASA. Thanks in advance for your help!C871:
    version 15.0
    no service pad
    service timestamps debug datetime msec localtime
    service timestamps log datetime msec localtime
    service password-encryption
    hostname router
    boot-start-marker
    boot-end-marker
    enable password 7 xxxx
    aaa new-model
    aaa session-id common
    clock timezone UTC -8
    clock summer-time PDT recurring
    dot11 syslog
    ip source-route
    ip dhcp excluded-address 192.168.2.1
    ip dhcp excluded-address 192.168.2.2
    ip dhcp pool dhcp-vlan2
       network 192.168.2.0 255.255.255.0
       default-router 192.168.2.1
    ip cef
    ip domain name xxxx.local
    no ipv6 cef
    multilink bundle-name authenticated
    password encryption aes
    username xxxx password 7 xxxx
    ip ssh version 2
    interface FastEthernet0
    switchport mode trunk
    interface FastEthernet1
    interface FastEthernet2
    interface FastEthernet3
    interface FastEthernet4
    description WAN Interface
    ip address 1.1.1.2 255.255.255.252
    ip access-group wna-in in
    no ip redirects
    no ip unreachables
    no ip proxy-arp
    ip nat outside
    ip virtual-reassembly
    duplex auto
    speed auto
    no cdp enable
    interface Vlan1
    no ip address
    interface Vlan2
    description LAN-192.168.2
    ip address 192.168.2.1 255.255.255.0
    ip nat inside
    ip virtual-reassembly
    interface Vlan10
    description router-asa
    ip address 10.10.10.1 255.255.255.252
    ip nat inside
    ip virtual-reassembly
    ip forward-protocol nd
    no ip http server
    no ip http secure-server
    ip nat inside source list nat-pat interface FastEthernet4 overload
    ip nat inside source static 10.10.10.1 interface FastEthernet4
    ip nat inside source static udp 10.10.10.2 500 interface FastEthernet4 500
    ip nat inside source static udp 10.10.10.2 4500 interface FastEthernet4 4500
    ip nat inside source static esp 10.10.10.2 interface FastEthernet4
    ip route 0.0.0.0 0.0.0.0 1.1.1.1
    ip route 10.10.10.0 255.255.255.252 10.10.10.2
    ip route 192.168.2.0 255.255.255.0 10.10.10.2
    ip access-list standard ssh
    permit 0.0.0.0 255.255.255.0 log
    permit any log
    ip access-list extended nat-pat
    deny   ip 192.168.2.0 0.0.0.255 192.168.100.0 0.0.0.255
    permit ip 192.168.2.0 0.0.0.255 any
    ip access-list extended wan-in
    deny   ip 192.168.0.0 0.0.255.255 any
    deny   ip 172.16.0.0 0.15.255.255 any
    deny   ip 10.0.0.0 0.255.255.255 any
    deny   ip 127.0.0.0 0.255.255.255 any
    deny   ip 169.255.0.0 0.0.255.255 any
    deny   ip 255.0.0.0 0.255.255.255 any
    deny   ip 224.0.0.0 31.255.255.255 any
    deny   ip host 0.0.0.0 any
    deny   icmp any any fragments log
    permit tcp any any established
    permit icmp any any net-unreachable
    permit udp any any eq isakmp
    permit udp any any eq non500-isakmp
    permit esp any any
    permit icmp any any host-unreachable
    permit icmp any any port-unreachable
    permit icmp any any packet-too-big
    permit icmp any any administratively-prohibited
    permit icmp any any source-quench
    permit icmp any any ttl-exceeded
    permit icmp any any echo-reply
    deny   ip any any log
    control-plane
    line con 0
    exec-timeout 0 0
    logging synchronous
    no modem enable
    line aux 0
    line vty 0 4
    access-class ssh in
    exec-timeout 5 0
    logging synchronous
    transport input ssh
    scheduler max-task-time 5000
    end
    ASA:
    ASA Version 9.1(2)
    hostname asa
    domain-name xxxx.local
    enable password xxxx encrypted
    xlate per-session deny tcp any4 any4
    xlate per-session deny tcp any4 any6
    xlate per-session deny tcp any6 any4
    xlate per-session deny tcp any6 any6
    xlate per-session deny udp any4 any4 eq domain
    xlate per-session deny udp any4 any6 eq domain
    xlate per-session deny udp any6 any4 eq domain
    xlate per-session deny udp any6 any6 eq domain
    passwd xxxx encrypted
    names
    ip local pool vpn-pool 192.168.100.10-192.168.100.35 mask 255.255.255.0
    interface Ethernet0/0
    switchport trunk allowed vlan 2,10
    switchport mode trunk
    interface Ethernet0/1
    switchport access vlan 2
    interface Ethernet0/2
    shutdown
    interface Ethernet0/3
    shutdown
    interface Ethernet0/4
    shutdown
    interface Ethernet0/5
    shutdown
    interface Ethernet0/6
    shutdown
    interface Ethernet0/7
    shutdown
    interface Vlan1
    no nameif
    no security-level
    no ip address
    interface Vlan2
    nameif inside
    security-level 100
    ip address 192.168.2.2 255.255.255.0
    interface Vlan10
    nameif outside
    security-level 0
    ip address 10.10.10.2 255.255.255.252
    ftp mode passive
    clock timezone UTC -8
    clock summer-time PDT recurring
    dns server-group DefaultDNS
    domain-name xxxx.local
    object network vlan2-mapped
    subnet 192.168.2.0 255.255.255.0
    object network vlan2-real
    subnet 192.168.2.0 255.255.255.0
    object network vpn-192.168.100.0
    subnet 192.168.100.0 255.255.255.224
    object network lan-192.168.2.0
    subnet 192.168.2.0 255.255.255.0
    access-list no-nat-in extended permit ip 192.168.2.0 255.255.255.0 192.168.100.0 255.255.255.0
    access-list vpn-split extended permit ip 192.168.2.0 255.255.255.0 any
    pager lines 24
    logging enable
    logging asdm informational
    mtu inside 1500
    mtu outside 1500
    no failover
    icmp unreachable rate-limit 1 burst-size 1
    no asdm history enable
    arp timeout 14400
    no arp permit-nonconnected
    nat (inside,outside) source static lan-192.168.2.0 lan-192.168.2.0 destination static vpn-192.168.100.0 vpn-192.168.100.0 no-proxy-arp route-lookup
    object network vlan2-real
    nat (inside,outside) static vlan2-mapped
    route outside 0.0.0.0 0.0.0.0 10.10.10.1 1
    timeout xlate 3:00:00
    timeout pat-xlate 0:00:30
    timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02
    timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00 mgcp-pat 0:05:00
    timeout sip 0:30:00 sip_media 0:02:00 sip-invite 0:03:00 sip-disconnect 0:02:00
    timeout sip-provisional-media 0:02:00 uauth 0:05:00 absolute
    timeout tcp-proxy-reassembly 0:01:00
    timeout floating-conn 0:00:00
    dynamic-access-policy-record DfltAccessPolicy
    user-identity default-domain LOCAL
    aaa authentication ssh console LOCAL
    aaa authentication http console LOCAL
    http server enable
    http 192.168.2.0 255.255.255.0 inside
    http 10.10.10.1 255.255.255.255 outside
    no snmp-server location
    no snmp-server contact
    snmp-server enable traps snmp authentication linkup linkdown coldstart warmstart
    crypto ipsec ikev1 transform-set ESP-AES-256-SHA esp-aes-256 esp-sha-hmac
    crypto ipsec security-association pmtu-aging infinite
    crypto dynamic-map SYSTEM_DEFAULT_CRYPTO_MAP 65535 set pfs group1
    crypto dynamic-map SYSTEM_DEFAULT_CRYPTO_MAP 65535 set ikev1 transform-set ESP-AES-256-SHA
    crypto dynamic-map SYSTEM_DEFAULT_CRYPTO_MAP 65535 set reverse-route
    crypto map outside_map 65535 ipsec-isakmp dynamic SYSTEM_DEFAULT_CRYPTO_MAP
    crypto map outside_map interface outside
    crypto ca trustpool policy
    crypto ikev1 enable outside
    crypto ikev1 policy 30
    authentication pre-share
    encryption aes-256
    hash sha
    group 2
    lifetime 86400
    telnet timeout 5
    ssh 192.168.2.0 255.255.255.0 inside
    ssh 10.10.10.1 255.255.255.255 outside
    ssh timeout 20
    ssh version 2
    ssh key-exchange group dh-group1-sha1
    console timeout 0
    threat-detection basic-threat
    threat-detection statistics access-list
    no threat-detection statistics tcp-intercept
    webvpn
    anyconnect-essentials
    group-policy vpn internal
    group-policy vpn attributes
    dns-server value 8.8.8.8 8.8.4.4
    vpn-tunnel-protocol ikev1
    split-tunnel-policy tunnelspecified
    split-tunnel-network-list value vpn-split
    default-domain value xxxx.local
    username xxxx password xxxx encrypted privilege 15
    tunnel-group vpn type remote-access
    tunnel-group vpn general-attributes
    address-pool vpn-pool
    default-group-policy vpn
    tunnel-group vpn ipsec-attributes
    ikev1 pre-shared-key xxxx
    class-map inspection_default
    match default-inspection-traffic
    policy-map type inspect dns preset_dns_map
    parameters
      message-length maximum client auto
      message-length maximum 512
    policy-map global_policy
    class inspection_default
      inspect dns preset_dns_map
      inspect ftp
      inspect h323 h225
      inspect h323 ras
      inspect ip-options
      inspect netbios
      inspect rsh
      inspect rtsp
      inspect skinny 
      inspect esmtp
      inspect sqlnet
      inspect sunrpc
      inspect tftp
      inspect sip 
      inspect xdmcp
      inspect icmp
    service-policy global_policy global
    prompt hostname context
    no call-home reporting anonymous
    call-home
    profile CiscoTAC-1
      no active
      destination address http https://tools.cisco.com/its/service/oddce/services/DDCEService
      destination address email [email protected]
      destination transport-method http
      subscribe-to-alert-group diagnostic
      subscribe-to-alert-group environment
      subscribe-to-alert-group inventory periodic monthly
      subscribe-to-alert-group configuration periodic monthly
      subscribe-to-alert-group telemetry periodic daily
    Cryptochecksum:40c05c90210242a42b7dbfe9bda79ce2
    : end

    Hi,
    I think, that you want control all outbound traffic from the LAN to the outside by ASA.
    I suggest some modifications as shown below.
    C871:
    interface Vlan2
    description LAN-192.168.2
    ip address 192.168.2.2 255.255.255.0
    no ip nat inside
    no ip proxy-arp
    ip virtual-reassembly
    ip access-list extended nat-pat
    no deny ip 192.168.2.0 0.0.0.255 192.168.100.0 0.0.0.255
    no permit ip 192.168.2.0 0.0.0.255 any
    deny ip 192.168.2.0 0.0.0.255 any
    permit ip 10.10.10.0 0.0.0.255 any
    ASA 5505:
    interface Vlan2
    nameif inside
    security-level 100
    ip address 192.168.2.1 255.255.255.0
    Try them out and response.
    Best regards,
    MB

  • Issues with Archiving object MM_EKKO

    Hi,
    I am trying to archive few Purchasing documents on R3 4.7, The archiving write job fails with the error
    "There is no entry for instance 000000000096197571 in either INOB or IBase"
    Please help.
    Regards,
    Deepak

    If people need to look/work with archived data, then you need the infostructures, except you use the archive add-ons from PBS  ( http://www.pbs-software.com/PBS-Startseite.1.0.html?&L=1 ) which allow you do see archive data by using the well-known SAP transactions, without the need of space-consuming SAP infostructures.
    I try my best to avoid infostructures, means I archive data that is no needed for business, not needed to be looked up often.  (developing infostructure or even programs to analyse data that was archived early is more expensiv than the costs of the disk space, at least in our branch)
    But if an infostructure is given by SAP, then you can activate (fill it) or deactivate (delete content) within a few seconds with tiny effort. So I do it in rare cases if somebody needs to see archived data.

  • Mass deletion of batches - SAP Archiving Object MM_SPSTOCK

    __SAP Archiving Object MM_SPSTOCK (Batches and Special Stocks)__
    Would like to know if there is any standard program or report available through which the batches (to be deleted) can be set with a deletion flag. We are in the process of implementing the archiving object MM_SPSTOCK and the batches have not been flagged. There is no pre-processing job for MM_SPSTOCK that can be used to set the deletion flag for all eligible batches.
    This object MM_SPSTOCK does not have any date or selection criteria for the write job. All batches with set deletion flag will be archived/deleted.
    We are in the process of implementing LO_CHVW (Batch where-used data) for which imlementing MM_SPSTOCK is a pre-requisite.
    Would appreciate any leads around this. Any other suggestions around the MM_SPSTOCK & LO_CHVW will be great.
    Thanks
    Sam

    I am basically looking for a method (program / report) through which mass deletion flag can be set for eligible batches prior to using MM_SPSTOCK archiving object to archving / deleting the batches.
    Thanks
    Sam

  • Problem during Rate Routing Upload using BDC.

    Dear Sir/Madam,
    I am uploading Rate Routings using a BDC program which is working perfectly but having a single problem.
    In the initial screen of the transaction CA21(Create Rate Routing), I need to enter only the Material Number and its Plant and all the other fields should be left blank.
    But, here the group number field is automatically getting filled with the previous value and it is incrementing the group counter number. 
    I want the system to allocate different group number for  each Routing. I want the group number to be unique.
    Thanks,
    Ranjan.

    Dear Ranjan,
    While doing recording CA21. you would pass only the material number and plant (i mean you did recording of CA21 based on material number as well as plant not for routing number (group counter))
    Routing number (group counter) dynamic (In your case Internal number rage has assigned).
    So the Problem is:
    1st record of you internal table update smoothly because you program will pass only material and plant
    group counter (RC271-PLNNR) field is blank, after update 1st record system will regenerates the
    group counter number.
    ones the system updates the data it will generates Group counter number and assign to filed :(RC271-PLNNR).
    after saving the record system will go loop statement of you program. again program will call the call transaction statement with 2nd record of the internal table. call transaction statement pass the material number and plant field at ca21. but group counter number automatically poulated in the screen field because that time system can't be refresh the initial screen of CA21,
    so system will shows previous updated screen ( 1st routing record will show)
    Remove your bdc perform and add this code in your BDC perform.
    *        Start new screen                                              *
    FORM BDC_DYNPRO USING PROGRAM DYNPRO.
       CLEAR BDCDATA.
       BDCDATA-PROGRAM  = PROGRAM.
       BDCDATA-DYNPRO   = DYNPRO.
       BDCDATA-DYNBEGIN = 'X'.
       APPEND BDCDATA.
    ENDFORM.
    *        Insert field                                                  *
    FORM BDC_FIELD USING FNAM FVAL.
       IF FVAL <> SPACE.
         CLEAR BDCDATA.
         BDCDATA-FNAM = FNAM.
         BDCDATA-FVAL = FVAL.
         APPEND BDCDATA.
       ENDIF.
    *                Clearing the Group Counter                                *
       IF FVAL = SPACE.
         CLEAR BDCDATA.
         BDCDATA-FNAM = FNAM.
         BDCDATA-FVAL = FVAL.
         APPEND BDCDATA.
       ENDIF.
    above code: 1st time of call transaction FVAL = space means ( group counter field is blank)
    2nd and rest of the time FVAL <> space. means (previous record group number exists for new call transaction ) so system will be by pass with new record.
    Check with debugging mode. you will come to whats going in you code.
    Even i have go same problem while uploading routing data. i have find out solution after doing my RND.
    Regards,
    Akshath

  • 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

  • Problems with a Java socket client

    Hi, I'm using the following piece of code to recieve from a C++ server a string of chars: TcpCli = new Socket(m_HostIP, m_HostPorta); String msg=""; int lenSocketBuffer=0; BufferedInputStream in = new BufferedInputStream(TcpCli.getInputStream()); len

  • Using Row Type in Stored Procedure

    Hi, I am working on ADF technology wherein I need to call Procedure from javacode. I am using Jdev 11g version. I am using Entity Impl to invoke my Stored Procedure which I have used Row Type in it. This procedure is running Independently using Toad.

  • Cannot connect to iTunes and  YouTube

    I'm using iPad4, suddenly I cannot go to App Store and YouTube! I can't even use FaceTime, Facebook! The App Store shows 'cannot connect to iTunes' , YouTube shows 'load error', FaceTime and Facebook all shows account password wrong, but I'm sure rig

  • Can't connect to Wi-Fi, can't open Safari or view emails

    First off I cannot connect to any Wi-Fi and I have connected to Wi-Fi many times from the same locations.  Secondly when I try to open Safari, I first get a blank page (like the one you would either type in an address or search), then my bookmarks fl

  • Unable to acess dashboards

    Hi, i am unable to access the dashboards when i login with user -- Administrator. The error is Access Prohibited You do not have permission to any of the pages on this Dashboard.