XI scenario documentation
Hi Guys,
I am looking for a template to document XI scenarios. - Such as adapter type, structures, volume etc.
I have been going through a lot of posts without any luck as most of them has dead links in them. So please do not refere to old posts. Thanks!
Hi,
Please refer the following links:
Technical Infrastructure in SAP XI:
http://help.sap.com/bp_bpmv130/documentation/planning/technicalinfrasture.pdf
Integrating systems using SAP XI and Message flow:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/9928db90-0201-0010-6894-ffa53bf77672
adapters:
http://help.sap.com/saphelp_nw04/helpdata/en/ae/d03341771b4c0de10000000a1550b0/frameset.htm
Regards,
Nithiyanandam
Similar Messages
-
Personnel Cost Planning Scenario documentation..
Hi all,
If anyone of you have done Personnel Cost planning..then I will really appreciate any kind of documentation on it It will help me greatly as a reference as we are starting a new project on the same.
willinuk "at-the-rate" gmail.com
Help much appreciated,
Rgds,
WillsHi,
Try this.
Personnel administration
http://help.sap.com/saphelp_nw04/helpdata/en/63/351e3c6a2fc036e10000000a114084/frameset.htm
HR pre configured scenarios here.
http://help.sap.com/bp_biv170/
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/505351fe-ec8c-2910-c5b5-a43bbf53f6fc
Thanks,
JituK -
SCM APO IDES Scenarios documentation
Hi guys
Can any one tell me where I can find SCM APO IDES documentation on help.com? I am able to find the R3 IDES scenarios help documentation but not APO
Thanks in advance
AntonHi,
Follow this link
[http://help.sap.com/saphelp_apo/helpdata/en/7e/63fc37004d0a1ee10000009b38f8cf/frameset.htm|APO HELP]
http://help.sap.com/saphelp_apo/helpdata/en/7e/63fc37004d0a1ee10000009b38f8cf/frameset.htm
Hope this will help you
Regards,
Ashish
Edited by: A. A. Vaidya on Sep 11, 2009 3:49 PM -
Hi,
I am trying File 2 File scenario, I have file adapter(both receiver and sender ) installed on my machine.
And I have also 2 communication channels set, I used File adapters in communication channels. When I run this scenario, in Monitor I see my message to be processed sucessfully but I don't see any log in receiver adapter and also no output file.
I have selected File system and not FTP in receiver channel, does this selection creates output file on server disk?
If anyone have File2File scenario documentation, please forward it to me.
regards,
MustafaHi Jason,
I used the said config details, my input file is..
<?xml version="1.0" encoding="UTF-8" ?>
<ns0:MTYP_name xmlns:ns0="File_File">Mustafa</ns0:MTYP_name>
I am just doing simple mapping of single field, but I am getting the following error..
<b>
<SAP:Code area="INTERNAL">HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code>
<SAP:P1>500</SAP:P1>
<SAP:P2>internal server error: com.sap.aii.messaging.mo.MalformedMessageException: Cannot find Main Header in XMBMessage - check the message version</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText><html> <head> <title>Transport Service Error</title> </head> <body> <h1>HTTP/1.0 500</h1> <h3>internal server error: com.sap.aii.messaging.mo.MalformedMessageException: Cannot find Main Header in XMBMessage - check the message version</h3> </body> </html></SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP response contains status code 500 with the description internal server error: com.sap.aii.messaging.mo.MalformedMessageException: Cannot find Main Header in XMBMessage - check the message version XML tag Envelope missing in SOAP message header (SAP XI Extension)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error></b>
What is the cause of this error and also how do I change the trace logging levels?
regards,
Mustafa -
Hi,
Can anyone send me LO640 Foreign Trade to email: [email protected]?
Also can you please mail me foreign trade scenarios/documentation as well?
Points will be rewarded. ThanksHi,
Please find below online documentation related to Foreign Trade.
http://help.sap.com/saphelp_47x200/helpdata/en/93/74440d546011d1a7020000e829fd11/frameset.htm
<b>Reward if helpful.</b>
Thanks -
Business process exchange of documents in B2B scenarios.
Hello,
I need some documents which lists the process of exchanging of business documents like orders ,ordrsp ASN,DESADV, ....INVRPT ..
What is the sequence of this process in case of a B2B?
I am not sure whether i posted the document in correct forum or not .
But some guidance/help in this will be appreciated...
Thanks in Anticipation
RajeshHi Rajesh,
please check here [ALE/IDoc Interface: Application Scenarios|http://help.sap.com/saphelp_erp60_sp/helpdata/en/af/7e844367c24d4a950df3205052769d/frameset.htm]
and here [Electronic Data Interchange / IDoc Interface (SD-EDI)|http://help.sap.com/saphelp_erp60_sp/helpdata/en/af/1210377eff2e7ae10000009b38f889/frameset.htm] for a more technical look at the topic.
Depending on the industry you work in you might also want to take a look at the scenario documentation in the best practices section of the respectiv industry that also include information on the exchange of documents: [SAP Best Practices|http://help.sap.com/]
-> industry package
-> industry xx
-> business information
-> preconfigured scenarios
Regards,
Andi -
I want to "Restore Factory Content" on my T61. Is the procedure documented?
I have seen that I can press Thinkvantage button while in bootup, then follow instructions. Is the scenario documented anywhere so I can see in advance what I will be doing?
it is pretty straight forward, it is all pretty much automated.... just select restore your system, then restore my hard drive to the original factory state. Everything else is self explanatory.
Regards,
Jin Li
May this year, be the year of 'DO'!
I am a volunteer, and not a paid staff of Lenovo or Microsoft -
Best Datasources to use for Sales Orders and Invoiced Quantities
Hello Experts,
Just wanted to ask if anyone has experience and can recommended the ECC Datasources to use to extract:
1. Invoiced Qty = Sales History
2. Open Sales Orders
3. Shipped Qty= Goods issued but not yet invoiced
So far in my research I have down the following datasources:
1. 2LIS_13_VDITM Billing Document Item Data for Invoiced Quantities
2. 2LIS_11_SSL, or 2LIS_11_SCL or 2LIS_11_VASCL for Open Sales Orders
3. 2LIS_12_VCITM, 2LIS_11_V_SSL for Shipped Quantities
Any suggestions?
Thanks alot
VictoriaHi Victoria:
Plese take a look at SAP Best Practices (Scenario Documentation and Building Blocks)
Open this URL: http://help.sap.com/bp_bw370/html/index.htm
Click "Preconfigured Scenarios" link
Click on the Links to navigate on the different available scenarios and to see the documents you can download (Technical Documentation > Configuration Guide)
*Customer Relationship Management
-- Sales Analysis
-- Cross-Functional Analysis: Financial and Sales Data
-- Booking Billing Backlog Analysis
-- Sales Planning
-- Scheduling Agreements Analysis
-- CRM Analytics
Edited by: Francisco Milan on Jun 3, 2010 6:23 PM -
Reg:implementation Enterprise portal in solution manager
hi all
i am new to the concept of solution manager .In this how can we implement Enterprise portal .Actually what an EP consultant work need to be done in this solution manager.can any one provide some real time scenarios info related to it .
regards
DeepikaHi,
Regarding the implementation phase, Solution Manager helps you via several functionalities:
- Solution Documentation: Central documentation of processes, system landscape, custom code,...
- Test Management:Change impact analysis, End-to-end test management
- Change Control Management: Integrated quality management, Synchronized transports of various components, Controlled and documented adjustment of business processes incl. approval process
- Application Incident Management: Integrated service desk, Involvement of partners in problem resolution, Provide root-cause analysis for complex landscapes with diverse technology stacks
The most important part in from my perspective for a implementation consultant is the Project Documentation functionality, where you can get Implementation Content for Enterprise Portal. This includes business scenarios documentation and business process included in the Business Process Repository, how to configure different scenarios and business processes, test cases, etc.
I think you can find some information in the marketplace about this functionality. For example you may find something under service.sap.com/alm -> SAP Solution Manager and Tools.
Best regards,
Fernando -
Error with dual boot Win 8/OL6 R3
Hello,
I am hoping to discuss this with someone who has experience with this configuration. My goal is to get Oracle Linux dual booting on my windows 8 machine.
I have installed OL but I am having trouble getting it to dual boot win8/OL using the windows boot menu. Whereas windows 8 boots as expected, the Oracle Linux option gives me the error:
"+Windows failed to start. A recent hardware or software change might be the cause...contact you system administrator or computer manufacturer for assistance+
+File:+ \NST\nst_linux.mbr
+Status: 0xc000007b+
+Info: The selected application or operating system couldn't be loaded because a required file is missing or contains errors.+"
Here are some details of the scenario:
- Documentation followed: Red_Hat_Enterprise_Linux-6-Installation_Guide-en-US.pdf
- Hardware: Dell Precision M4700 64 bit UEFI
- OEM installed/Default OS: Windows 8 Pro 64 bit
- Installation source: OracleLinux-R6-U3-Server-x86_64-dvd.iso (written to DVD)
These are the broad steps I followed:
In windows 8
I:
- downloaded the Linux ISO software. The checksum on the download matched
- wrote the ISO to a bootable installation disk
- created a new 344gb partition for Linux using the DOS DISKPART command - partition 7
Linux Install
- I booted using the Linux installation DVD and started the installation
- When Installing Linux partition 7 became a 500mb system partition and partition 8 became the 343 gb Linux partition
- I manually created the boot partition as ext3 (because the pdf I was following said "+If your 64-bit x86 system uses UEFI instead of BIOS, you will need to manually create a /boot partition. This partition must have an ext3 file system. If you choose to partition automatically, your system will not boot.+"
- I installed the boot loader on sda7. I selected “First sector of boot partition - /dev/sda7”. I assume this installs separate GRUB boot loader on the Linux partition (7) – which will then be 'chain loaded' from the windows boot menu. Put another way, it will boot with the windows boot manager, which will give me an option to chain load the Grub boot loader, which will then run Linux...
- I chose the desktop installation
- The installation reported that it completed successfully
I successfully booted back into windows:
- I used easybcd to edit the microsoft bcd and successfully created a boot menu for Oracle Linux. I used the legacy grub because the Linux documentation says "+Note that the version of GRUB in Red Hat Enterprise Linux 6 is an old and stable version now known as "GRUB Legacy" since upstream development moved to GRUB 2.3 Red Hat remains committed to maintaining the version of GRUB that we ship with Red Hat Enterprise Linux 6, just as we do with all packages that we ship.+".
- After installing Linux and updating the BCD, the BCD now looks like this:
Windows Boot Manager
identifier {bootmgr}
path \EFI\Microsoft\Boot\bootmgfw.efi
description Windows Boot Manager
locale en-US
inherit {globalsettings}
integrityservices Enable
default {current}
resumeobject {2b56acdd-8bbe-11e2-9ba6-b8ca3ad88679}
displayorder {current}
{524cc0d3-8bce-11e2-935f-b8ca3ad88679}
toolsdisplayorder {memdiag}
timeout 30
Windows Boot Loader
identifier {current}
device partition=C:
path \Windows\system32\winload.efi
description Windows 8
locale en-US
inherit {bootloadersettings}
recoverysequence {524cc0d1-8bce-11e2-935f-b8ca3ad88679}
integrityservices Enable
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \Windows
resumeobject {2b56acdd-8bbe-11e2-9ba6-b8ca3ad88679}
nx OptIn
bootmenupolicy Standard
Real-mode Boot Sector
identifier {524cc0d3-8bce-11e2-935f-b8ca3ad88679}
device partition=C:
path \NST\nst_linux.mbr
description OracleLinux
I'm not sure the BCD entry is correct. I assume that this entry should be pointing to the nst_linux.mbr on the Linux boot partition. However I have verified that this file exists in windows 8:
C:\NST\nst_linux.mbr
I haven't been able to exactly confirm how the boot process should work i.e. whether this file should actually be in the Linux boot partition (as opposed to the windows c drive) and whether the BCD should also point to the Linux boot partition when referring to this partition.
As I mentioned above, I now have the windows boot menu with Windows 8 (which boots successfully) and Oracle Linux (which gives me the error see below for complete wording**). Is the Real-mode Boot sector wrong? Should it point to the Linux boot partition? Is it a problem with my UEFI disk? I don't think it should be because this version of Oracle Linux supports UEFI and my hardware is UEFI.
Has anyone carried out a similar win8/OL dual boot?
2001
** Complete wording of the Linux boot option in the windows boot manager:
Windows failed to start. A recent hardware or software change might be the cause. To fix the problem:
1. Insert your Windows installation disk and restart the computer.
2. Choose your language settings, and then click "next".
3. Click "Repair your computer".
If you do not have this disk, contact you system administrator or computer manufacturer for assistance
File: \NST\nst_linux.mbr
Status: 0xc000007b
Info: The selected application or operating system couldn’t be loaded because a required file is missing or contains errors.
Edited by: 2001 on Apr 1, 2013 4:27 PM
Edited by: 2001 on Apr 17, 2013 5:17 PMHi,
Here are my responses:
*[asmirnov]* Could you please confirm, I just want to see if I got it right the first time -
*[2001]* I'm happy to share my progress
Q1)
*[asmirnov]* You did create a partition (where you would install Linux) from Win8, correct?
*[2001]* Yes. I used diskmgmt.msc to create a separate partition. I didn't format the partition because the Linux install doesn't want that, it creates and formats the partitions in the unallocated partition
Q2)
*[asmirnov]* You use GRUB (not GRUB2)?
*[2001]* I'm not sure where you were asking about, so I hope my answer here covers all possibilities you may have meant.
I was using the windows 8 boot. I wanted to chain load to the boot loader in the Linux Partition. It is interesting what the Linux install did with my partition, it created 2 partitions in the unformatted partition. 1 was a bootable partition and the other was the Linux partition. The details were:
2 sda’s (a boot / ext4 and a VolGroup (vg_linuxlocalhost)/ physical volume (LVM) ). In the VolGroup it created 3 lv’s, lv_root, lv_home and lv_swap. I understand that this is all normal.
I followed the documentation note which said "To configure the Red Hat Enterprise Linux boot loader to chain load from a different boot loader, you must specify the boot drive manually. If you chose any of the automatic partitioning options, you must now select the Review and modify partitioning layout option before you click Next or you cannot specify the correct boot drive"
So there was also the note in the documentation that said "Note that the version of GRUB in Red Hat Enterprise Linux 6 is an old and stable version now known as "GRUB Legacy" since upstream development moved to GRUB 2.3 Red Hat remains committed to maintaining the version of GRUB that we ship with Red Hat Enterprise Linux 6, just as we do with all packages that we ship." I didn't install any bootloaders manually (either the windows 8 OOTB default that came with my machine or the Linux one), I just took the defaults. I'm wasn't sure how to access the Linux partitions once it is installed, so I can't confirm it was the legacy GRUB in the Linux boot partition, but I believe this note is saying that it OL6 does use the legacy grub. I believe GRUB Legacy is version .97.
Q3)
*[asmirnov]* Which version of Linux exactly did you use, was that Oracle Linux or you used one from RedHat directly? What is the kernal version?
*[2001]* I used "OracleLinux-R6-U3-Server-x86_64-dvd.iso.sha1sum" from the mirror site http://mirror.aarnet.edu.au/pub/oraclelinux/OL6/U3/x86_64/. According to the release notes at: https://oss.oracle.com/ol6/docs/RELEASE-NOTES-U3-en.html the kernel is
- Unbreakable Enterprise Kernel Release 2 [kernel-uek-2.6.39-200.24.1.el6uek]. Installed and booted by default
- Red Hat compatible Kernel [kernel-2.6.32-279.el6]. Installed by default
Note: By default, both the Unbreakable Enterprise Kernel and the Red Hat Compatible Kernel for the specific architecture (i386 or x86_64) are installed, and the system boots the Unbreakable Enterprise Kernel by default. If needed, /etc/grub.conf and /etc/sysconfig/kernel can be modified to make the system boot with the Red Hat Compatible Kernel by default.
Regarding your follow-up point that "Microsoft blocks 3rd party chainloaders from the BCD menu for UEFI machines. We are researching workarounds, none have presented themselves as of yet.", I'm not sure it actually blocks it, but it certainly isn't a straight forward process.
I have actually abandoned my attempt to get the dual boot working. It is a real shame because I wanted to do it for my own satisfaction.
I am now using Oracle Virtual Box as suggested by others, include Dude earlier in this thread. This has given me confidence that I was doing all the right things because the install worked first time without any problems. The virtualization is much simpler and I have had no problems so far.
Fusion
As for your point about the fusion middleware and OL5. I am looking at Oracle SOA with is part of the Fusion brand. I think that the latest SOA components will work on OL6 - but I have yet to try it. Following the certification matrix can be a little difficult. So as I indicated above, my current thoughts are to use the Oracle Virtual Box with Linux r6 u3 and to install the SOA components on that when I get chance. The alternative is using the pre-built virtual machine it has Linux and SOA (it might cover your stack too, or there may be another one that suits you better on the site) http://www.oracle.com/technetwork/middleware/soasuite/learnmore/vmsoa-172279.html. Note that this is still on OL5.
I hope this helps. -
Version Control for adobe forms
Dear All,
We have a situation where we already go live with version 0 of our adobe form. Now, we have an enhancement to the form i.e.: some new functionalities and new field. Previously we have tried to transport the new changes to the production without any version control and those processes that have been already started prior to the new changes encounter error when the user continues the process.
I am wondering how do the version control works and any documentation on how to configure it?
Thanks in advance
Regards,
BryanHi Brian,
Here is some information that I found in the IMG on Create ISR Scenario...
Create ISR Scenario
Use
In this IMG activity, you create an ISR scenario that has a one-to-one relationship with a form scenario. To be able to use a form scenario in a process, one ISR scenario must exist for each form scenario. The ISR scenario and the form scenario must be linked with each other. You make this setting in Customizing for HR Administrative Services in the IMG activity Link ISR Scenario with Form Scenario.
In the form scenario, you define primarily the basic set of form fields and their processing through the backend services. In the ISR scenario, you specify the definition of the user interface. You also specify which form is used for the display and how the layout of this interactive form is designed. You use interactive forms based on Adobe software to create and process the forms.
ISR scenarios and form scenarios are version dependent. The version numbers of the ISR scenario are assigned automatically. Note that a form scenario must have exactly the same version as the linked ISR scenario. For this reason, you should always create a new version in the ISR scenario first and then use the same version number when you create a version in the form scenario manually.
Note
If an ISR scenario or form scenario (with an existing version) has already been used in a productive process, you should not change the configuration. If you want to make changes to a process or an ISR scenario or form scenario, you should always create a new version, and only ever use that new version in the future. In this way, processes that have been started can be concluded with the old version and new processes can be started simultaneously with the new version.
This is from the Create Form Scenario documentation...
Create version
Form scenarios are version dependent, which means that there is at least one version of each form scenario. Versions are linked with processes. Since processes can vary, you must also be able to adjust the associated scenarios. To be able to provide different forms for process variants, you create versions.
You can still process and change an existing version at a later point in time. Once a version has been used to execute a process, you should not make any more changes to this version; instead, you should create a new version.
The form scenario and the (linked) ISR scenario are both version dependent. They must always have exactly the same version numbers. Note that the version number of the ISR scenario is generated and cannot be entered manually. When you create a new version in the form scenario, you therefore have to use the version number generated in the ISR scenario.
If you have already made extensive Customizing settings for the form scenario and want to create a new version based on the settings, you should use the IMG activity Manage Form Scenario.
Hope this helps...
Cheers,
Kevin -
Upgrade APO 3.0 to SCM 5.0 SR2 (requirements in source system)
Hello!:
We want to do and upgrade upgrade APO 3.0 to SCM 5.0 SR2
And we have seen the Guides SCM5.0 SR2 and SCM5.0 SR3, but appears info in the page 26 only about check the software requirements from APO 3.0 to SR3, but we want to check the information about APO3.0 to SR2.
Regards,
Alfredo.Alfredo,
This is not a easy question, since you are several releases behind on APO. I have done upgrade from APO 3.0 to SCM 4.1 and then subsequently to 5.0 so there were lots of learnings specific to the Projects and develoments. The Setup being different in different industries and companies, there is no one answer to this question. Try the following ...
- Read the Release Notes of SCM 3.1, 4.0, 4.1, 5.0. You will see a Host of New Functionalities - Newer in SNP, PPDS, TPVS, Master Data (PDS along with PPMs).
I do not know what functionality you are live with in APO 3.0.
On the Existing Setup that you may find changed, I remember the following big changes ...
- GUI Changes are galore in master data, less
- SNP Side - Changes in TLB Engine & TLB Prioritization.
- Deployment Split Functionality
- Changes in User Exits (old code would not work). You will find this painfull if you've implemented User Exits. eg : If you were determining OrderTypes in orders sent from APO to R3. TLB User Exits. Lesser changes in Masterdata userexits.
- Newer fields in Master Data (eg : SNP Checking Horizon in Product Master and it's implications on Deployment & TLB. ).
- Subcontracting Planning in APO.
- Enhancements in VMI.
- Use of Parallel Processing for all Modules planning.
- Enhancements in Aggregated Planning
- Enhancements in Product Interchangeability.
- Several Newer Functionalities like ICH to make/replace the earlier Collaborative Planning better.
- Master Data several changes (eg : PDS)
- Several improvements in CoreInterface Function and Que Issues. In 4.0 onwards there is new functionality around CIF Postprocessing
- Use of Process Chains to streamline Batch Jobs and especially BI Loads into Cubes and Planning Areas.
- Several enhancements in PPDS (newer heuristics), Alerts
- BW underwent a Major change from BW 2.0 to BW 3.0 to now BI 7.0 which impacts Setup for Demand Planning. eg : The InfoCube got renamed to InfoProviders.
I suggest you start with the Release Notes. Form a List of your Test Scenarios, then Upgrade in your Development and start to Test. Don't plan less, but more time for testing since you are undergoing a several releases change. First start to get your Existing Business Scenarios documented as Test Scripts in Order.
I STRONGLY recommend doing a Technical Upgrade Only (i.e : do not upgrade Major Functionality unless there is no other way). In Summary for SURE SCM 5.0 is a Much better and Stable System than APO 3.0.
Hope this helps. Reward Points If you find it usefull.
Regards,
Ambrish Mathur -
Hello!
Does anyone know of a BTE where the accounting document number of a posted document is available?
I need the BTE to be triggered immediately after the document is posted.
Appreciate you help.
Salai.HI,
Sivaprakesh,
I am new to BTE i have worked out on one scenario i was successfully completed but, after reading your question may intention is to do more scenarios on BTE but unfortunately i couldn't find any scenario on BTE i very much thank ful to u if u can send Your requirement /scenario documentation.
Thank u,
Shabeer ahmed. -
Call (consume) a webservice from ABAP for dummies
Hi
I find the documentation for this topic very confusing. It a badly structured mix of documentation of client scenarios, server scenarios and worst of all a lot of XI nonsense.
I need purely client scenario documentation without any info about XI and without any info about creating web services.
I just need to know how to consume a web based webservice in ABAP program. Where can I find this docu?
I have tried to generate proxies from different WSDL sources, but it always fails with different error messages.
Can anyone suggest a simple WSDL webservice usefull for testing my setup?
Best regards
Thomas Madsen NielsenYou are right, the help files do mix consuming and creating, but they do provide a list of steps for consuming and what you need to do. To consume a web service, the general steps you need to follow are:
- Create an extendable package with use accesses SAI_SXMS, SAI_TOOLS, SAPPINT
- Create a proxy class using the wizard in SE80 (right click on the package -> Create -> Enterprise Service) - the creation of the class depends on the WSDL document - you can either generate based on the url for the WSDL or download the WSDL document and import it as a file in the wizard. You may need to tinker with the WSDL document to get the class generation to complete successfully. Your WSDL is here: [http://maptp12.map24.com/map24/webservices1.5?soap=Map24Routing]
- Create a logical port in LPCONFIG or SOAMANAGER (assumes NW 7.0 SP14 or later) with information in the WSDL
- Create a program to consume the service method - it will look something like this (abbreviated):
DATA: gv_client_proxy TYPE REF TO zcwsbb_co_global_weather_soap,
gv_sys_exception TYPE REF TO cx_ai_system_fault.
DATA: gs_request TYPE zcwsbb_get_weather_soap_in,
gs_response TYPE zcwsbb_get_weather_soap_out,
gs_weather TYPE zst_currentweather.
DATA: gv_message TYPE string.
TRY.
CREATE OBJECT gv_client_proxy.
CALL METHOD gv_client_proxy->get_weather
EXPORTING
input = gs_request
IMPORTING
output = gs_response.
CATCH cx_ai_system_fault INTO gv_sys_exception.
CALL METHOD gv_sys_exception->if_message~get_text
RECEIVING
result = gv_message.
WRITE: gv_message.
FREE: gv_client_proxy, gv_sys_exception.
EXIT.
ENDTRY.
- Transform the response as required using ST or XSLT -
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.
SAPs 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 companys 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
-
Problem installing Palm Desktop on Windows Vista.
I am trying to install PalmDesktopWin414 on a couple different computers that are both running Windows Vista Ultimate. At the palmOne InstallShield Wizard welcome screen it generates the following error. Internal Error 2738. This interrupts the insta
-
Illustrator CC 17.0.1 crashing on start-up MAC
The last two days I've been unable to open Illustrator CC 17.0.1 on Mac OS 10.9. I've copied the crash message below. I've tried to hold command, option + shift on startup to delete the prefs, but it doesn't even get that far. I've also re-booted in
-
My daughter forgot her password and we took it to Apple for a restore. When they did that it wiped it clean except the email address and password attached. Now, she can not remember her id and password for login to even go through set up. So, does an
-
Library - Lightroom or Elements?
I just can't figure this out on my own and haven't been able to find an aswer. I have about 4000 images in the Elements organizer. Now that I have Lightroom, what should I be doing with the files that are already on my computer and in the Elements or
-
I have a statement like this , which is taking a lot of time. SELECT MATNR DATAB KNUMH FROM A005 APPENDING TABLE IT_COND FOR ALL ENTRIES IN IT_ZCOSTHISTFINAL WHERE KAPPL = 'V' AND KSCHL = 'PR00' AND MATNR = IT_ZCOSTHISTFINAL-MATNR. how can i improve