BW Documents requested
Hi all,
Can anyone send me the BW documents related to extraction, reporting, configuring metadata, performance tuning etc .
Thanks in Advance
Phani K Bandaru
Hi michael/Bandaru/Surya/Meps,
can you please send the Documents to me as well. Please send them to [email protected]
Thanks in Advance,
Dilse...
Harish
Similar Messages
-
When attempting to log in to the web site the following message is received. This web site works
on other systems using Firefox.
This server could not verify that you are authorized to access the document requested. Either you supplied the wrong credentials (e.g., bad password), or your browser doesn't understand how to supply the credentials required.
Additionally, a 401 Authorization Required error was encountered while trying to use an ErrorDocument to handle the request.
== URL of affected sites ==
http://www.mdyc.org/members_onlyYou may have saved a bad password so Firefox is entering that rather than giving you the option to try again. Go to Tools > Options > Security > Saved Passwords and delete the saved passwords for that site and then try logging in again.
-
PDF Document requests a password for opening despite not setting it up to do so
I created a secure pdf document that is to be downloaded from a web site. Upon downloading, users should be able to open/view the pdf without having to enter a password, but would need a password to be able to edit or make changes to the document. When testing the document and downloading from the web site, I am prompted for a password even though I did not set the pdf to request one for opening the document.
Can someone please help me undertand what's going on. I've tried a million things with no luck!
Thanks!Can you post the file somewhere for us to look at?
-
Hi Experts,
Could you please tell me, how to pass XML document as a request string to the webservice scenario. Inside the service, I have to do the schema validation for the request . Please guide me, how to proceed further?
Regards
SaraHi SARA,
use following Code written in SAX parsing .this will fulfil your requirment.This handle Special character also.
import java.io.File;
import java.io.FileInputStream;
import java.io.FileOutputStream;
import java.io.IOException;
import java.io.InputStream;
import java.io.OutputStream;
import java.io.OutputStreamWriter;
import java.io.Writer;
import java.util.ArrayList;
import java.util.Calendar;
import java.util.GregorianCalendar;
import java.util.HashMap;
import java.util.List;
import java.util.Map;
import javax.xml.parsers.FactoryConfigurationError;
import javax.xml.parsers.ParserConfigurationException;
import javax.xml.parsers.SAXParser;
import javax.xml.parsers.SAXParserFactory;
import org.xml.sax.Attributes;
import org.xml.sax.helpers.DefaultHandler;
import org.xml.sax.SAXException;
import com.sap.aii.mapping.api.StreamTransformation;
import com.sap.aii.mapping.api.StreamTransformationException;
public class SimpleForwardMappingString extends DefaultHandler implements StreamTransformation
private List m_arlCurrent = new ArrayList();
private List m_arlBOList = new ArrayList();
private List m_arlObjectList = new ArrayList();
public static int counter = 0;
String listName = "newList";
public StringBuffer m_totalElementsBuffer = new StringBuffer();
String startData = "<inCanonStream>";
String endData = "</inCanonStream>";
private Map param = null;
/** Constant Strings used in Forward Mapping */
public static void main(String args[])
try {
InputStream in = new FileInputStream(new File("C:
Documents and Settings
281152
Desktop
Cannonical12321.xml"));
OutputStream out = new FileOutputStream(new File("C:
Documents and Settings
281152
Desktop
Cannonical21.xmlOut.xml"));
SimpleForwardMappingString myMapping = new SimpleForwardMappingString();
catch (Exception e)
e.printStackTrace();
public void execute(InputStream arg0, OutputStream arg1)
throws StreamTransformationException
Writer out;
try
out = new OutputStreamWriter(arg1, "UTF16");
/** Building the SAX parser */
getXMLDoc(arg0, arg1);
arg1.write(m_totalElementsBuffer.toString().getBytes("UTF16"));
catch (IOException e)
System.out.println("Error : io" + e.getMessage());
catch (Exception e)
System.out.println("Error :" + e.getMessage());
/* (non-Javadoc)
@see com.sap.aii.mapping.api.StreamTransformation#setParameter(java.util.Map)
public void setParameter(Map arg0)
public void getXMLDoc(InputStream inputStream, OutputStream outputStream)
Defines a factory API that enables applications to configure and
obtain a SAX based parser to parse XML documents. Once an application
has obtained a reference to a SAXParserFactory it can use the
factory to configure and obtain parser instances.
SAXParserFactory factory = SAXParserFactory.newInstance();
try
factory.setNamespaceAware(true);
factory.setValidating(true);
SAXParser saxParser = factory.newSAXParser();
Parse the content of the given {@link java.io.InputStream}
instance as XML using the specified
{@link org.xml.sax.helpers.DefaultHandler}.
@param inputstream InputStream containing the content to be parsed.
@param cobject The SAX DefaultHandler to use.
@exception IOException If any IO errors occur.
@exception IllegalArgumentException If the given InputStream is null.
@exception SAXException If the underlying parser throws a
SAXException while parsing.
saxParser.parse(inputStream, this);
catch (FactoryConfigurationError e)
System.out.println("Error");
catch (ParserConfigurationException e)
e.printStackTrace();
catch (SAXException e)
e.printStackTrace();
catch (IOException e)
e.printStackTrace();
/** ===========================================================
Methods Overriding in SAX Default Handler
===========================================================
Receive notification of the beginning of the document.
By overriding this method in a subclass to take specific actions
at the beginning of a document (such as allocating the root node
of a tree or creating an output file)
public void startDocument()throws SAXException
if(m_totalElementsBuffer.length()>0)
m_totalElementsBuffer = new StringBuffer();
counter = 0;
m_totalElementsBuffer.append(m_prologue);
m_totalElementsBuffer.append(m_nameSpace);
m_totalElementsBuffer.append(startData); }
Receive notification of the end of the document.
By overriding this method in a subclass to take specific
actions at the end of a document (such as finalising a tree
or closing an output file)
public void endDocument()throws SAXException
m_totalElementsBuffer.append(endData);
m_totalElementsBuffer.append(m_rootElementEnd);
Receive notification of the start of an element.
By overriding this method in a subclass to take specific
actions at the start of each element (such as allocating
a new tree node or writing output to a file)
public void startElement(String namespaceURI, String name, String qName, Attributes attrs)
throws SAXException
/** If current List is not empty then append node to StringBuffer */
m_totalElementsBuffer.append("<" + name + ">");
Receive notification of the end of an element.
By overriding this method in a subclass to take specific
actions at the end of each element (such as finalising
a tree node or writing output to a file)
public void endElement(String uri, String name, String qName) throws SAXException
m_totalElementsBuffer.append("</" + name + ">");
Receive notification of character data inside an element.
By overriding this method to take specific actions for each
chunk of character data (such as adding the data to a node
or buffer, or printing it to a file)
public void characters(char buf[], int offset, int len)
throws SAXException
String s = new String(buf, offset, len);
if (null != s && s.length() >0)
if(s.equalsIgnoreCase("&"))
//System.out.println("FOUND AND SYMBOL");
String s1 = s.replaceAll("&","_-#_");
//System.out.println("s= " +s1);
s = s1;
if(s.equalsIgnoreCase("<"))
//System.out.println("FOUND AND SYMBOL");
String s1 = s.replaceAll("<","_#-_");
//System.out.println("s= " +s1);
s = s1;
m_totalElementsBuffer.append(s);
Thanks
Sunil Singh -
Is there any way to create a field that will auto increment i.e. document request id field?
I would like to have a "Request #" automatically assigned to a form. Is there any way to do that?
We currently don't support this type of field. You can vote for this feature request here: http://forums.adobe.com/ideas/1047
We use this to help prioritize our work.
Randy -
Abap certification 4.6B to 4.6C Relevant documents requested
Hi all,
I prepared ABAP 4.6B (2000) certification material for my ABAP Certification. After I find that 4.6B exam is not available and they said only 4.6C (2003) available. Please can any one list the exact differences in between these two exams (I found that the difference is ABAP Objects - BC 401). Please confirm this and let me know if we have any other differences. Please provide the BC-401 document ( Mail it to [email protected]). I am struck at the moment.
Please provide me any other info and other suggetions.Hello Mallela
There should not be a big difference in the exams between 4.6B and 4.6C.
Even at the Netweaver exam (6.40) which I passed 10 month ago a big portion of the questions were dealing with "basic" stuff. I you have not taken any exams yet I like to mention that you do not have to write down any answers but it is a multiple-choice test:
- either a single answer is correct (then you will see radio-buttons at each possible answer) or
- serveral answers are correct (checkboxes)
Sample question: "Which modifications are possible with sorted internal tables?" => Of course you cannot append to such a table but must insert your entries.
So, if you have a firm stand on BC430 (ABAP Dictionary), have developed quite a lot (-> BC400 basics of ABAP) and have some general understanding of ABAP-OO (BC401) you will be on the safe side. Also, have a general knowledge of the SAP Technology (guess corresponding to BC050) like the client-server technology.
Official documents like the BC401 documents cannot be shared because SAP would not allow this. In any case, you will find plenty of information in the SAP online help.
Finally, I highly recommend the weblog "ABAP 46C to 640 Delta Training" (/people/thomas.jung3/blog/2005/05/15/abap-46c-to-640-delta-training) by Thomas Jung, mainly as appetizer for you when you make the switch from 4.6x to 6.40.
Regards
Uwe -
Authorizer cant change document request for approval
Hi ,
Is there any methods to enable the Authorizer to change the A/R Invoice that sent for their approval.
E.g. Change the Unit Price, GL Code or add more items
System Info: SBO 2007A PL 45HI Experts,
I have a similar requirement, we have configured a one level approval template with a single authorizer. After the draft is sent from the originator and before the approval is done by the authorizer any attempt at changing the data in the draft returns an error stating "the draft is in approval process" however after the the draft is approved the authorizer is unable to change the document. The requirement is, during approval process, the authorizer has to make corrections in the document if any..... please let me know if there are any settings that needs to be checked for this to occur.
tha -
E- Recruitment Document Request please
Hi all, could any one send me some document or screen shots for E-Recruitment please mail id: vivassnaz at yahoo dot com
Vignesh,
check these links
http://help.sap.com/saphelp_erp60_sp/helpdata/en/72/c9b54015c4752ae10000000a155106/frameset.htm
EREC 600-http://help.sap.com/saphelp_erp60_sp/helpdata/en/72/c9b54015c4752ae10000000a155106/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/45/8150635e9c40c1e10000000a1553f7/frameset.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/30adcac6-7a55-2a10-9fa9-a61d947f6ec9
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a07122ae-8216-2a10-c9a5-996717a0648b
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/24396589-0a01-0010-3c8c-ab2e3acf6fe2
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/erphcm/sap%2be-recruiting
E-Recruitment-SAP E-Recruiting
Thanks
Bala Duvvuri -
Updating CustromXML part in documents on request
Hello,
I have a document library, which contains .docx files with content controls, bound to custom XML. I need to update those custom XML parts with the new values when user requests file open operation. I can do it by writting my own HTTPHandler for GET, but
it only works if the user downloads a file. If users access it via Word, it communicates with the service via CellStorage.svc.
I cannot use VSTO plug-ins in my environment. So, no web-service option or anything like that. I tried to cheat with "External" package relationship for my custom xml part, but it's not supported by the MS Word. Is there any seam in the system
where I can intercept all document open requests and replace required custom XML part on the fly? If not, what would be a preferred solution?
Thanks for you help in advance.Hi,
According to your description, my understanding is that want to intercept open document request to update custom xml part of word file in a SharePoint document library.
I suggest you can track the open document request using Fiddler, in my environment, the open document request can be tracked, then you can do your custom code in the httpmodule.
Here are some similar thread for your reference:
http://sharepoint.stackexchange.com/questions/76515/intercept-file-open-event-and-execute-custom-code
http://sharepoint.stackexchange.com/questions/54046/intercepting-sharepoint-open-document-request
Thanks
Best Regards
Forum Support
Jerry Guo
TechNet Community Support -
The printer in firefox wants to print out a "3 page list of emails" and NOT the document I requested
The printer prompts in Firefox to print a document all appears as good same as in a Word or Excel Doc - which DOES print files properly.
In Mozilla FF the document requested will produce a list of ~ 3 pages of my emails or NOT the document requested.
== This happened ==
Every time Firefox opened
== About 3 or 4 months backThanks Ed for your response. I use g mail if this helps.
It is weird as sometimes it will print correctly and most other times, not. Greg
Message:
File > Print Preview will display what Firefox is going to print.
1. Firefox doesn't do email, so you are probably referring to problems with a web mail service - which one?
2. Without us having access to that same web mail service we would have to guess about what your problem is - I can only guess that there is a button to display a "printer ready" version of an email that you need to use so the email you are reading is displayed all by itself and thus only that is printed. -
Problem in calling Document Style Web Service
Hi,
I have just downloaded the demos.zip available for WebServices on otn.
I have deployed the stateful document webservice on the Oracle 10g AS
Also i have followed all the steps mentioned in the UTL_DBWS callout utility.
But i am confused with the setting of the request & response XMLTYPE for a webservice.
I am attaching the code in which i have used to call a webservice kindly tell me if there is anything wrong in my approach
CREATE OR REPLACE FUNCTION DOC_WBSRVC_TEST
RETURN VARCHAR2
AS
SERVICE_ UTL_DBWS.SERVICE;
CALL_ UTL_DBWS.CALL;
SERVICE_QNAME UTL_DBWS.QNAME;
PORT_QNAME UTL_DBWS.QNAME;
XOPERATION_QNAME UTL_DBWS.QNAME;
XSTRING_TYPE_QNAME UTL_DBWS.QNAME;
RESPONSE XMLTYPE;
REQUEST XMLTYPE;
BEGIN
--UTL_DBWS.SET_HTTP_PROXY ('172.17.24.12:8080');
SERVICE_QNAME :=
UTL_DBWS.TO_QNAME
('http://psc-pc0592.corp.satyam.ad/statefuldocws/docservice?WSDL',
'StatefulDoc'
SERVICE_ := UTL_DBWS.CREATE_SERVICE (SERVICE_QNAME);
CALL_ := UTL_DBWS.CREATE_CALL (SERVICE_);
UTL_DBWS.SET_TARGET_ENDPOINT_ADDRESS
(CALL_,
'http://psc-pc0592.corp.satyam.ad/statefuldocws/docservice'
UTL_DBWS.SET_PROPERTY (CALL_, 'SOAPACTION_USE', 'TRUE');
UTL_DBWS.SET_PROPERTY (CALL_, 'SOAPACTION_URI', 'urn:oracle:startShopping');
UTL_DBWS.SET_PROPERTY (CALL_, 'OPERATION_STYLE', 'DOCUMENT');
REQUEST :=
XMLTYPE
( '<n:startShopping xmlns:n="urn:oracle:startShopping">'
|| '</n:startShopping>'
RESPONSE := UTL_DBWS.INVOKE (CALL_, REQUEST);
RETURN RESPONSE.EXTRACT
('//startShoppingOutput/child::text()',
'xmlns="http://psc-pc0592.corp.satyam.ad/statefuldocws/docservice"'
).GETSTRINGVAL ();
END;
Thanks & Regards,
MDHi Aviad,
thanks for your fast reply.
But in Web Service Navigator my Web Service is not shown, because I used the SOAP Adapter.
<b>My Web Service link:</b>
http://<host>:<port>/XISOAPAdapter/MessageServlet?channel=:SRV_GBD_WS_GET_DEB_DETAIL:CC_GBD_WEBSERVICE_SENDER&version=3.0&Sender.Service=&Interface=%5E*
During executing Web Dynpro I got following errors:
1. 'The system cannot find the path specified'.
2. com.sap.tc.webdynpro.model.webservice.exception.WSModelRuntimeException: Exception on creation of service metadata for WSDL URL
Regards,
Mario -
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 -
How i can add document nu in below query
i want to add one field in below query
field is bkpf-xblnr
i want document number after d_text.
here d_text = 'Payment for'
CLEAR: tab_out-value,tab_out-name.
READ TABLE tab_out WITH KEY 'D_TEXT'.
tab_out-value = d_text.
MODIFY tab_out INDEX sy-tabix.
please help
thanks in advanced.hi help yar i m totaly new for this
i m pasting whole code here just see yar and where u changing please hight light that things
thanks yar
PROGRAM zfisp0001.
*& Subroutine pool ZFISP0001 *
*& Author: Rakesh Rao on 01.04.05 *
*& Modified by: Rakesh Rao on 15.07.2005 *
*& Description: This subroutine pool is called from Check and Payment *
*& Advice SAPScripts *
TABLES: itcsy.
TYPES: BEGIN OF t_itcsy.
INCLUDE STRUCTURE itcsy.
TYPES: END OF t_itcsy.
DATA: tab_in TYPE STANDARD TABLE OF t_itcsy WITH NON-UNIQUE
DEFAULT KEY INITIAL SIZE 0.
DATA: tab_out TYPE STANDARD TABLE OF t_itcsy WITH NON-UNIQUE
DEFAULT KEY INITIAL SIZE 0.
DATA: d_count(3) VALUE 0,
d_netamt_tot TYPE p DECIMALS 2,
d_tdsamt_tot TYPE p DECIMALS 2,
d_grossamt_tot TYPE p DECIMALS 2,
d_tdsamt TYPE p DECIMALS 2.
DATA flag.
DATA: bschl LIKE bseg-bschl.
DATA: shkzg LIKE bseg-shkzg.
clear: d_count,d_netamt_tot.
*& Form ZPAYMENT
text
--> p1 text
<-- p2 text
FORM zpayment TABLES tab_in STRUCTURE itcsy
tab_out STRUCTURE itcsy.
tables : bsak.
TYPES: imis_type_c20(20) TYPE c,
imis_type_c10(10) TYPE c.
DATA: l_intern TYPE imis_type_c20.
DATA: e_intern TYPE imis_type_c10.
DATA: i_extern TYPE imis_type_c10.
DATA: d_belnr(10),
D_VBLNR(10),
d_bukrs TYPE bseg-bukrs,
d_gjahr TYPE bseg-gjahr,
d_gjahr1 TYPE bseg-gjahr, " 15.07.2005 Rakesh
d_buzei TYPE bseg-buzei,
d_augbl TYPE bseg-augbl,
d_umskz TYPE bseg-umskz,
d_bschl TYPE bseg-bschl,
d_bktxt TYPE bkpf-bktxt,
d_budat(10),
d_rebzg TYPE bseg-rebzg,
D_SHKZG TYPE REGUP-SHKZG,
d_swnes TYPE regud-swnes,
d_netamt TYPE p DECIMALS 2,
d_tdsamt TYPE p DECIMALS 2,
d_discamt TYPE regud-wskto,
d_gross TYPE regud-wrbtr.
DATA: BEGIN OF t_bkpf,
bukrs TYPE bkpf-bukrs,
belnr TYPE bkpf-belnr,
gjahr TYPE bkpf-gjahr,
budat TYPE bkpf-budat,
bktxt TYPE bkpf-bktxt,
xblnr TYPE bkpf-xblnr,
END OF t_bkpf.
DATA: BEGIN OF t_bseg,
bukrs TYPE bseg-bukrs,
belnr TYPE bseg-belnr,
gjahr TYPE bseg-gjahr,
buzei TYPE bseg-buzei,
umskz TYPE bseg-umskz,
bschl TYPE bseg-bschl,
qbshb TYPE bseg-qbshb,
augbl TYPE bseg-augbl,
rebzg TYPE bseg-rebzg,
rebzj TYPE bseg-rebzj,
sgtxt TYPE bseg-sgtxt,
xref1 TYPE bseg-xref1,
ebeln TYPE bseg-ebeln,
shkzg type bseg-shkzg,
END OF t_bseg.
DATA: num VALUE ' ',
d_result VALUE ' '.
DATA: d_symbol VALUE '/',
d_text(11) VALUE 'Payment for'.
DATA: d_belnr1 LIKE bseg-belnr.
DATA: wa_payrq TYPE payrq. " 15.07.2005 Rakesh
18.05.2006
data : wa_belnr like bseg-belnr,wa_augbl like bseg-augbl.
18.05.2006
06.09.2006
data : d_other type p decimals 2.
Read incoming data
*break-point.
*zpayment.
CLEAR: d_belnr,d_bukrs,d_gjahr,d_result.
clear d_tdsamt.
Company code
CLEAR tab_in-value.
READ TABLE tab_in WITH KEY 'REGUP-BUKRS'.
d_bukrs = tab_in-value.
Document number
CLEAR tab_in-value.
READ TABLE tab_in WITH KEY 'REGUP-BELNR'.
wa_belnr = d_belnr(10) = tab_in-value(10).
Posting Key
CLEAR tab_in-value.
READ TABLE tab_in WITH KEY 'REGUP-BSCHL'.
d_bschl = tab_in-value.
Special G/L Indicator
CLEAR tab_in-value.
READ TABLE tab_in WITH KEY 'REGUP-UMSKZ'.
d_umskz = tab_in-value.
Fiscal year
CLEAR tab_in-value.
READ TABLE tab_in WITH KEY 'REGUP-GJAHR'.
d_gjahr = tab_in-value.
<-- 15.07.2005 Rakesh
Fiscal year1 - For Payment request case
CLEAR tab_in-value.
READ TABLE tab_in WITH KEY 'REGUD-GJAHR'.
d_gjahr1 = tab_in-value.
15.07.2005 Rakesh -->
Document item
CLEAR tab_in-value.
READ TABLE tab_in WITH KEY 'REGUP-BUZEI'.
d_buzei = tab_in-value.
Discount amount, if any
CLEAR tab_in-value.
READ TABLE tab_in WITH KEY 'REGUD-WSKTO'.
REPLACE ALL OCCURRENCES OF ',' IN tab_in-value WITH ' '.
d_discamt = tab_in-value.
Gross Amount
CLEAR tab_in-value.
READ TABLE tab_in WITH KEY 'REGUD-WRBTR'.
REPLACE ALL OCCURRENCES OF ',' IN tab_in-value WITH ' '.
d_gross = tab_in-value.
Gross Amount
CLEAR tab_in-value.
READ TABLE tab_in WITH KEY 'REGUD-WNETT'.
REPLACE ALL OCCURRENCES OF ',' IN tab_in-value WITH ' '.
d_netamt = tab_in-value.
Clearing document 18.05.2006
CLEAR tab_in-value.
READ TABLE tab_in WITH KEY 'REGUP-VBLNR'.
wa_augbl = tab_in-value.
DEBIT/CREDIT INDICATOR
CLEAR tab_in-value.
READ TABLE tab_in WITH KEY 'REGUP-SHKZG'.
d_SHKZG = tab_in-value(1).
IF d_netamt < 0 AND D_SHKZG = 'S'.
D_NETAMT = D_NETAMT * '-1'.
ENDIF.
Check document no. is clearing document than reset wnett = 0.
18.05.2006
select single * from bsak where augbl = wa_augbl
and bukrs = d_bukrs and gjahr = d_gjahr1.
if sy-subrc = 0 and wa_belnr = wa_augbl.
d_netamt = 0.
endif.
18.05.2006
Check if Down payment request
IF d_bschl = '39'.
This line item is not considered
d_result = 'X'.
ELSE.
Check if Down payment
IF d_bschl = '29'
and wa_augbl = wa_belnr. "18.05.2006
IF d_umskz EQ 'A'
OR d_umskz EQ 'B'
OR d_umskz EQ 'I'
OR d_umskz EQ 'M'
OR d_umskz EQ 'D'.
Put Document Number of the Payment Document value to 'd_belnr'
CLEAR tab_in-value.
READ TABLE tab_in WITH KEY 'REGUP-VBLNR'.
d_belnr = tab_in-value.
ENDIF.
ENDIF.
<--15.07.2005 Rakesh
Check if Payment request exists in 'payrq'
CLEAR wa_payrq.
Convert 'd_belnr' to 10 digits,if required
CLEAR: l_intern,e_intern.
CALL 'CONVERSION_EXIT_ALPHA_INPUT' ID 'INPUT' FIELD d_belnr
ID 'OUTPUT' FIELD l_intern.
e_intern = l_intern+10.
d_belnr1 = d_belnr.
CLEAR d_belnr.
d_belnr = e_intern.
SELECT SINGLE keyno augbl FROM payrq
INTO CORRESPONDING FIELDS OF wa_payrq
WHERE keyno = d_belnr.
IF sy-subrc = 0. " Yes
Take clearing document which is the required accounting document
d_belnr = wa_payrq-augbl.
Convert 'd_belnr' to 10 digits,if required
CLEAR: l_intern,e_intern.
CALL 'CONVERSION_EXIT_ALPHA_INPUT' ID 'INPUT' FIELD d_belnr
ID 'OUTPUT' FIELD l_intern.
e_intern = l_intern+10.
CLEAR d_belnr.
d_belnr = e_intern.
Assign 'd_gjahr1' to 'd_gjahr' as this is relevant here.
d_gjahr = d_gjahr1. " 15.07.2005 Rakesh
Get BSEG data
SELECT SINGLE bukrs belnr gjahr buzei augbl rebzg rebzj
sgtxt qbshb umskz bschl xref1 ebeln
FROM bseg INTO CORRESPONDING FIELDS OF t_bseg
WHERE bukrs EQ d_bukrs
AND belnr EQ d_belnr
AND gjahr EQ d_gjahr
AND buzei EQ d_buzei " not relevant
AND bschl EQ '25' " Posting key - Outgoing payment
AND koart EQ 'S' " G/L accounts
AND shkzg EQ 'S'. " Debit
ELSE. " No
For all other cases, we use this final logic, even though we have
taken d_belnr value from accounting doc no., in some earlier cases.
Put document number of the payment document(vblnr) value to 'd_belnr',
IF d_bschl = '29'
and wa_augbl <> wa_belnr. "18.05.2006
IF d_umskz EQ 'A'
OR d_umskz EQ 'B'
OR d_umskz EQ 'I'
OR d_umskz EQ 'M'
OR d_umskz EQ 'D'.
else.
CLEAR tab_in-value.
READ TABLE tab_in WITH KEY 'REGUP-VBLNR'.
d_belnr = tab_in-value.
endif.
else.
CLEAR tab_in-value.
READ TABLE tab_in WITH KEY 'REGUP-VBLNR'.
d_belnr = tab_in-value.
endif.
-->15.07.2005
Convert 'd_belnr' to 10 digits,if required
CLEAR: l_intern,e_intern.
CALL 'CONVERSION_EXIT_ALPHA_INPUT' ID 'INPUT' FIELD d_belnr
ID 'OUTPUT' FIELD l_intern.
e_intern = l_intern+10.
CLEAR d_belnr.
d_belnr = e_intern.
Get BSEG data
SELECT SINGLE bukrs belnr gjahr buzei augbl rebzg rebzj
sgtxt qbshb umskz bschl xref1 ebeln shkzg
FROM bseg INTO CORRESPONDING FIELDS OF t_bseg
WHERE bukrs EQ d_bukrs
AND belnr EQ d_belnr
AND gjahr EQ d_gjahr1
"changed by Bharat 15.04.2006 - d_gjahr1 contains payment doc fiscal yea
"r and d_gjahr contains invoice fiscal year
AND buzei EQ d_buzei "amisha 10-10-2005
AND bschl EQ '25' " Posting key - Outgoing payment
AND shkzg EQ 'S' "added by Bharat 17.04.2006
AND ( koart EQ 'K' OR koart EQ 'D').
<--15.07.2005 Rakesh
18.05.2006
in clearing document payment advice not consider TDS amount of
payment document
if wa_belnr <> wa_augbl and d_shkzg = 'S'.
t_bseg-qbshb = t_bseg-qbshb * '-1'.
d_netamt = d_netamt + t_bseg-qbshb.
t_bseg-qbshb = 0.
endif.
18.05.2006
ENDIF.
-->15.07.2005
Get corresponding BKPF data
If Down payment
IF d_bschl = '29'.
IF d_umskz EQ 'A'
OR d_umskz EQ 'B'
OR d_umskz EQ 'I'
OR d_umskz EQ 'M'
OR d_umskz EQ 'D'.
SELECT SINGLE bukrs belnr gjahr budat bktxt xblnr
FROM bkpf INTO CORRESPONDING FIELDS OF t_bkpf
WHERE bukrs EQ d_bukrs
AND belnr EQ d_belnr
AND gjahr EQ d_gjahr1.
"changed by Bharat 15.04.2006 - d_gjahr1 contains payment doc fiscal yea
"r and d_gjahr contains invoice fiscal year
ENDIF.
ELSE.
If Partial payment/On-account payment
IF t_bseg-augbl IS INITIAL.
On-Account case
IF t_bseg-augbl IS INITIAL.
IF t_bseg-rebzg IS INITIAL.
t_bseg-rebzg = t_bseg-belnr. " Payment Document Number
t_bseg-rebzj = t_bseg-gjahr. " Fiscal year
ENDIF.
ENDIF.
SELECT SINGLE bukrs belnr gjahr budat bktxt xblnr
FROM bkpf INTO CORRESPONDING FIELDS OF t_bkpf
WHERE bukrs EQ t_bseg-bukrs
AND belnr EQ t_bseg-rebzg
AND gjahr EQ t_bseg-rebzj.
ELSE.
FULL PAYMENT with Discount
clear d_tdsamt.
Following code added for GSPL by bharat06092006
if d_bukrs eq 'GSPL'.
DATA : V_TEXT(20) TYPE C.
V_TEXT = 'W%'.
SELECT SINGLE wrbtr FROM bseg
INTO d_tdsamt
WHERE bukrs EQ d_bukrs AND
belnr EQ d_belnr1 AND
gjahr EQ d_gjahr AND " Added by bharat on 10-04-2006 fiscal year
bschl EQ '50' AND
KTOSL EQ 'WIT' AND
QSSKZ NOT LIKE V_TEXT.
SELECT single wrbtr FROM bseg
INTO d_other
WHERE bukrs EQ d_bukrs AND
belnr EQ d_belnr1 AND
gjahr EQ d_gjahr AND " Added by bharat on 10-04-2006 fiscal year
bschl EQ '50' AND
KTOSL EQ 'WIT' AND
QSSKZ LIKE V_TEXT.
ELSE.
Added by bharat 06.09.2006
SELECT SINGLE wrbtr
FROM bseg INTO d_tdsamt
WHERE bukrs EQ d_bukrs
AND belnr EQ d_belnr1
AND gjahr EQ d_gjahr
" Added by bharat on 10-04-2006 fiscal year
AND bschl EQ '50' AND KTOSL EQ 'WIT'.
ENDIF.
SELECT SINGLE bukrs belnr gjahr budat bktxt xblnr
FROM bkpf INTO CORRESPONDING FIELDS OF t_bkpf
WHERE bukrs EQ d_bukrs
AND belnr EQ d_belnr
AND gjahr EQ d_gjahr1.
"changed by Bharat 15.04.2006 - d_gjahr1 contains payment doc fiscal yea
"r and d_gjahr contains invoice fiscal year
tab_in-value
*d_tdsamt_tot
ENDIF.
ENDIF.
IF sy-subrc = 0.
Sr. no. for Line items
d_count = d_count + 1.
ELSE.
Else, this line item is not considered
d_result = 'X'.
ENDIF.
ENDIF. " if d_bschl = '39'
Pass the output to the outgoing table 'tab_out', if 'd_result' is not
*set.
IF d_result = ' '.
Line count
CLEAR: tab_out-value,tab_out-name.
READ TABLE tab_out WITH KEY 'COUNT'.
tab_out-value = d_count.
MODIFY tab_out INDEX sy-tabix.
Result flag
CLEAR: tab_out-value,tab_out-name.
READ TABLE tab_out WITH KEY 'RESULT1'.
tab_out-value = d_result.
MODIFY tab_out INDEX sy-tabix.
Clearing document
CLEAR: tab_out-value,tab_out-name.
READ TABLE tab_out WITH KEY 'AUGBL'.
tab_out-value = t_bseg-augbl.
MODIFY tab_out INDEX sy-tabix.
IF d_bschl <> '29'.
On-Account case
IF t_bseg-augbl IS INITIAL.
IF t_bseg-rebzg IS INITIAL.
t_bseg-rebzg = t_bseg-belnr. " Payment Document Number
ENDIF.
ENDIF.
ELSE.
Payment document request
IF NOT t_bseg-ebeln IS INITIAL. " First preference
t_bseg-rebzg = t_bseg-ebeln.
ELSE.
t_bseg-rebzg = d_belnr.
ENDIF.
ENDIF.
Number of the Invoice the Transaction Belongs to
CLEAR: tab_out-value,tab_out-name.
READ TABLE tab_out WITH KEY 'REBZG'.
SHIFT t_bseg-rebzg LEFT DELETING LEADING num.
tab_out-value = t_bseg-rebzg.
MODIFY tab_out INDEX sy-tabix.
Document number - check use??
CLEAR: tab_out-value,tab_out-name.
READ TABLE tab_out WITH KEY 'BELNR'.
tab_out-value = d_belnr. " check!!
MODIFY tab_out INDEX sy-tabix.
Net amount
d_netamt = d_gross - d_discamt - t_bseg-qbshb.
Gross amount
d_gross = d_netamt + d_tdsamt + t_bseg-qbshb.
CLEAR: tab_out-value,tab_out-name.
READ TABLE tab_out WITH KEY 'NETAMT'.
tab_out-value = d_netamt.
SHIFT tab_out-value LEFT DELETING LEADING space.
MODIFY tab_out INDEX sy-tabix.
TDS Amount
IF t_bseg-qbshb IS INITIAL.
CLEAR: tab_out-value,tab_out-name.
READ TABLE tab_out WITH KEY 'TDSAMT'.
tab_out-value = d_tdsamt.
SHIFT tab_out-value LEFT DELETING LEADING space.
MODIFY tab_out INDEX sy-tabix.
Added by bharat 06.09.2006
CLEAR: tab_out-value,tab_out-name.
READ TABLE tab_out WITH KEY 'D_OTHER'.
tab_out-value = d_other.
SHIFT tab_out-value LEFT DELETING LEADING space.
MODIFY tab_out INDEX sy-tabix.
Added by bharat 06.09.2006
ELSE.
CLEAR: tab_out-value,tab_out-name.
READ TABLE tab_out WITH KEY 'TDSAMT'.
tab_out-value = t_bseg-qbshb.
SHIFT tab_out-value LEFT DELETING LEADING space.
MODIFY tab_out INDEX sy-tabix.
ENDIF.
*Calculate Total Net amount & TDS amount which is stored in Global
*memory and accessed later
from 'FORM Z_TOTAL_AMT'
d_netamt_tot = d_netamt_tot + d_netamt.
d_grossamt_tot = d_grossamt_tot + d_gross.
d_tdsamt_tot = d_tdsamt_tot + t_bseg-qbshb + d_tdsamt + d_other.
CLEAR: tab_OUT-value,tab_out-name.
READ TABLE tab_OUT WITH KEY 'NETAMT_TOT'.
tab_out-value = d_netamt_tot.
shift tab_out-value left deleting leading space.
MODIFY tab_out INDEX sy-tabix.
Document Header text
CLEAR: tab_out-value,tab_out-name.
READ TABLE tab_out WITH KEY 'BKTXT'.
IF d_bschl = '29'.
tab_out-value = t_bseg-sgtxt. " for down payment request
ELSE.
tab_out-value = t_bkpf-bktxt.
ENDIF.
MODIFY tab_out INDEX sy-tabix.
Reference Document Number - Header
CLEAR: tab_out-value,tab_out-name.
READ TABLE tab_out WITH KEY 'XBLNR'.
IF d_bschl = '29'.
tab_out-value = t_bseg-xref1. " for down payment request
ELSE.
tab_out-value = t_bkpf-xblnr.
ENDIF.
MODIFY tab_out INDEX sy-tabix.
Symbol '/'
CLEAR: tab_out-value,tab_out-name.
READ TABLE tab_out WITH KEY 'D_SYMBOL'.
tab_out-value = d_symbol.
MODIFY tab_out INDEX sy-tabix.
Text 'Payment for'
CLEAR: tab_out-value,tab_out-name.
READ TABLE tab_out WITH KEY 'D_TEXT'.
tab_out-value = d_text.
MODIFY tab_out INDEX sy-tabix.
CLEAR: tab_out-value,tab_out-name.
READ TABLE tab_out WITH KEY 'D_TEXT'.
tab_out-value = d_text.
tab_out-xblnr = t_bkpf-xblnr.
MODIFY tab_out by bkpf-xblnr INDEX sy-tabix.
Posting date
CLEAR d_budat.
CALL FUNCTION 'CONVERT_DATE_TO_EXTERNAL'
EXPORTING
date_internal = t_bkpf-budat
IMPORTING
date_external = d_budat
EXCEPTIONS
date_internal_is_invalid = 1
OTHERS = 2.
IF sy-subrc <> 0.
MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
CLEAR: tab_out-value,tab_out-name.
READ TABLE tab_out WITH KEY 'BUDAT'.
tab_out-value = d_budat.
MODIFY tab_out INDEX sy-tabix.
ELSE.
Result flag
CLEAR: tab_out-value,tab_out-name.
READ TABLE tab_out WITH KEY 'RESULT1'.
tab_out-value = d_result.
MODIFY tab_out INDEX sy-tabix.
ENDIF.
d_gross = d_netamt + d_tdsamt + t_bseg-qbshb.
CLEAR: tab_out-value,tab_out-name.
READ TABLE tab_out WITH KEY 'GROSSAMT'.
tab_out-value = d_gross.
SHIFT tab_out-value LEFT DELETING LEADING space.
MODIFY tab_out INDEX sy-tabix.
ENDFORM. " ZPAYMENT
*& Form zamtwords
text - If only 'Net Amount' is required
--> p1 text
<-- p2 text
FORM zamtwords TABLES tab_in STRUCTURE itcsy
tab_out STRUCTURE itcsy.
DATA: d_swnet TYPE regud-swnes, " take character format type
d_swnet1 TYPE bseg-dmbtr.
d_words(160),
d_words1(80),
d_words2(80).
<-- 21.05.2005
DATA: d_words(160),
d_words1(80) TYPE c,
d_words2(80) TYPE c.
DATA: len TYPE i.
<-- 21.05.2005
*zamtwords
CLEAR tab_in-value.
READ TABLE tab_in WITH KEY 'REGUD-SWNET'.
d_swnet = tab_in-value.
REPLACE ALL OCCURRENCES OF '*' IN d_swnes WITH ' '.
REPLACE ALL OCCURRENCES OF ',' IN d_swnet WITH ' '.
d_swnet1 = d_swnet.
CLEAR d_swnet.
PERFORM z_conv_amt USING d_swnet1 CHANGING d_swnet.
Return 'SWNET1' without commas
CLEAR: tab_out-value,tab_out-name.
READ TABLE tab_out WITH KEY 'SWNET1'.
d_swnet = d_swnet1.
tab_out-value = d_swnet.
MODIFY tab_out INDEX sy-tabix.
Amount in Indian currency format
CALL FUNCTION 'Z_SPELL_AMOUNT_INR'
EXPORTING
amount = d_swnet1
IMPORTING
rupees_str = d_words.
Adjust 'd_words' left aligned
SHIFT d_words LEFT DELETING LEADING space.
<-- 21.05.2005
Split 'd_words' into 'd_words1' and 'd_words2'
since 'DEFINE' in SAPScript displays maximum 80 characters
d_words1 = d_words(80).
d_words2 = d_words+80(80).
*CALL FUNCTION 'C147_STRING_SPLIT_AT_POSITION'
EXPORTING
i_string = d_words
i_position = 80
IMPORTING
E_HEAD = d_words1
E_TAIL = d_words2.
len = STRLEN( d_words ).
Only 80 characters can be passed to one SAPScript symbol
Split 'd_words' into 'd_words1' and 'd_words2'
since 'DEFINE' in SAPScript displays maximum 80 characters
Check if string split is required
IF len > 80.
d_words1 = d_words(80). " First 80
d_words2 = d_words+80(80). " Next 80
Introduce an initial space in 'd_words2' if 80th character in
'd_words1' is space, as this space is not considered when 'd_words1'
value is passed to the SAPScript, since we need proper spacing
between 'd_words1' and 'd_words2' in the Cheque layout.
IF d_words1+79(1) = ' '.
SHIFT d_words2 RIGHT BY 1 PLACES.
ENDIF.
ELSE.
d_words1 = d_words.
d_words2 = space.
ENDIF.
21.05.2005 -->
Amount in words1
CLEAR: tab_out-value,tab_out-name.
READ TABLE tab_out WITH KEY 'WORDS'.
tab_out-value = d_words1.
MODIFY tab_out INDEX sy-tabix.
Amount in words2
CLEAR: tab_out-value,tab_out-name.
READ TABLE tab_out WITH KEY 'WORDS1'.
tab_out-value = d_words2.
MODIFY tab_out INDEX sy-tabix.
ENDFORM. " zamtwords
*& Form z_address
text
--> p1 text
<-- p2 text
FORM z_address TABLES tab_in STRUCTURE itcsy
tab_out STRUCTURE itcsy.
DATA d_bukrs TYPE bseg-bukrs.
DATA: t_t001 TYPE t001,
t_adrc TYPE adrc.
CLEAR: tab_in-value,t_t001,t_adrc.
READ TABLE tab_in WITH KEY 'REGUP-BUKRS'.
d_bukrs = tab_in-value.
CALL FUNCTION 'K_READ_T001'
EXPORTING
i_bukrs = d_bukrs
IMPORTING
e_t001 = t_t001
EXCEPTIONS
not_found = 1
OTHERS = 2.
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ELSE.
CALL FUNCTION 'RTP_US_DB_ADRC_READ'
EXPORTING
i_address_number = t_t001-adrnr
I_NATION = ' '
I_READ_DB =
IMPORTING
e_adrc = t_adrc
EXCEPTIONS
not_found = 1
OTHERS = 2
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
CLEAR: tab_out-value,tab_out-name.
READ TABLE tab_out WITH KEY 'ADRC-NAME1'.
tab_out-value = t_adrc-name1.
MODIFY tab_out INDEX sy-tabix.
CLEAR: tab_out-value,tab_out-name.
READ TABLE tab_out WITH KEY 'ADRC-STREET'.
tab_out-value = t_adrc-street.
MODIFY tab_out INDEX sy-tabix.
CLEAR: tab_out-value,tab_out-name.
READ TABLE tab_out WITH KEY 'ADRC-CITY1'.
tab_out-value = t_adrc-city1.
MODIFY tab_out INDEX sy-tabix.
CLEAR: tab_out-value,tab_out-name.
READ TABLE tab_out WITH KEY 'ADRC-POST_CODE1'.
tab_out-value = t_adrc-post_code1.
MODIFY tab_out INDEX sy-tabix.
ENDIF.
ENDFORM. " z_address
*& Form z_total_amt
text
--> p1 text
<-- p2 text
FORM z_total_amt TABLES tab_in STRUCTURE itcsy
tab_out STRUCTURE itcsy.
CLEAR: tab_out-value,tab_out-name.
READ TABLE tab_out WITH KEY 'NETAMT_TOT'.
tab_out-value = d_netamt_tot.
SHIFT tab_out-value LEFT DELETING LEADING space.
MODIFY tab_out INDEX sy-tabix.
CLEAR: tab_out-value,tab_out-name.
READ TABLE tab_out WITH KEY 'TDSAMT_TOT'.
tab_out-value = d_tdsamt_tot.
SHIFT tab_out-value LEFT DELETING LEADING space.
MODIFY tab_out INDEX sy-tabix.
CLEAR: tab_out-value,tab_out-name.
READ TABLE tab_out WITH KEY 'GROSSAMT_TOT'.
tab_out-value = d_grossamt_tot.
SHIFT tab_out-value LEFT DELETING LEADING space.
MODIFY tab_out INDEX sy-tabix.
ENDFORM. " z_total_amt
*& Form Z_NET_AMT
text
-->TAB_IN text
-->TAB_OUT text
FORM z_net_amt TABLES tab_in STRUCTURE itcsy
tab_out STRUCTURE itcsy.
TYPES: imis_type_c20(20) TYPE c,
imis_type_c10(10) TYPE c.
DATA: l_intern TYPE imis_type_c20.
DATA: e_intern TYPE imis_type_c10.
DATA: i_extern TYPE imis_type_c10.
DATA: d_belnr(10),
d_bukrs TYPE bseg-bukrs,
d_gjahr TYPE bseg-gjahr,
d_umskz TYPE bseg-umskz,
d_bschl TYPE bseg-bschl,
d_dmbtr1 TYPE bseg-dmbtr,
d_dmbtr(17). "prb16052006
d_dmbtr1 like regud-swnes. "prb16052006
DATA d_amt TYPE char18.
DATA: BEGIN OF t_bseg OCCURS 10,
bukrs TYPE bseg-bukrs,
belnr TYPE bseg-belnr,
gjahr TYPE bseg-gjahr,
buzei TYPE bseg-buzei,
dmbtr TYPE bseg-dmbtr,
wrbtr TYPE bseg-wrbtr,
umskz TYPE bseg-umskz,
bschl TYPE bseg-bschl,
qbshb TYPE bseg-qbshb,
NEbtR TYPE BSEG-nebtr, "prb13052006
END OF t_bseg.
<-- 21.05.2005
DATA: d_words(160),
d_words1(80) TYPE c,
d_words2(80) TYPE c.
DATA: len TYPE i.
<-- 21.05.2005
DATA wa_payrq TYPE payrq. " 15.07.2005 Rakesh
Read incoming data
CLEAR: d_belnr,d_bukrs,d_gjahr.
Company code
CLEAR tab_in-value.
READ TABLE tab_in WITH KEY 'REGUP-BUKRS'.
d_bukrs = tab_in-value.
Document number
CLEAR tab_in-value.
READ TABLE tab_in WITH KEY 'REGUP-BELNR'.
d_belnr(10) = tab_in-value(10).
Posting Key
CLEAR tab_in-value.
READ TABLE tab_in WITH KEY 'REGUP-BSCHL'.
d_bschl = tab_in-value.
Special G/L Indicator
CLEAR tab_in-value.
READ TABLE tab_in WITH KEY 'REGUP-UMSKZ'.
d_umskz = tab_in-value.
Fiscal Year
CLEAR tab_in-value.
READ TABLE tab_in WITH KEY 'REGUD-GJAHR'. " Note
CHECK sy-subrc = 0.
d_gjahr = tab_in-value.
Check if Down payment
IF d_bschl = '29'.
IF d_umskz EQ 'A'
OR d_umskz EQ 'B'
OR d_umskz EQ 'I'
OR d_umskz EQ 'M'
OR d_umskz EQ 'D'.
Put Document Number of the Payment Document value to 'd_belnr'
CLEAR tab_in-value.
READ TABLE tab_in WITH KEY 'REGUP-VBLNR'.
d_belnr = tab_in-value.
ENDIF.
ENDIF.
Check if Down payment request
IF d_bschl = '39'.
Put Document Number of the Payment Document value to 'd_belnr'
CLEAR tab_in-value.
READ TABLE tab_in WITH KEY 'REGUP-VBLNR'.
d_belnr = tab_in-value.
ENDIF.
<--15.07.2005 Rakesh
Check if Payment request exists in 'payrq'
CLEAR wa_payrq.
Convert 'd_belnr' to 10 digits,if required
CLEAR: l_intern,e_intern.
CALL 'CONVERSION_EXIT_ALPHA_INPUT' ID 'INPUT' FIELD d_belnr
ID 'OUTPUT' FIELD l_intern.
e_intern = l_intern+10.
CLEAR d_belnr.
d_belnr = e_intern.
SELECT SINGLE keyno augbl FROM payrq
INTO CORRESPONDING FIELDS OF wa_payrq
WHERE keyno = d_belnr.
IF sy-subrc = 0. " Yes
Take clearing document which is the required accounting document
d_belnr = wa_payrq-augbl.
Convert 'd_belnr' to 10 digits,if required
CLEAR: l_intern,e_intern.
CALL 'CONVERSION_EXIT_ALPHA_INPUT' ID 'INPUT' FIELD d_belnr
ID 'OUTPUT' FIELD l_intern.
e_intern = l_intern+10.
CLEAR d_belnr.
d_belnr = e_intern.
Get BSEG data
SELECT bukrs belnr gjahr buzei augbl rebzg rebzj sgtxt dmbtr wrbtr
qbshb nebtr
FROM bseg INTO CORRESPONDING FIELDS OF TABLE t_bseg
WHERE bukrs EQ d_bukrs
AND belnr EQ d_belnr
AND gjahr EQ d_gjahr
AND buzei EQ d_buzei
AND bschl EQ '25'
AND koart EQ 'S' " G/L accounts
AND shkzg EQ 'S'. " Debit
ELSE. " No
For all other cases, we use this final logic, even though we have
taken d_belnr value from accounting doc no., in some earlier cases.
Put document number of the payment document(vblnr) value to 'd_belnr',
CLEAR tab_in-value.
READ TABLE tab_in WITH KEY 'REGUP-VBLNR'.
d_belnr = tab_in-value.
-->15.07.2005
Convert 'd_belnr' to 10 digits.
CLEAR: l_intern,e_intern.
CALL 'CONVERSION_EXIT_ALPHA_INPUT' ID 'INPUT' FIELD d_belnr
ID 'OUTPUT' FIELD l_intern.
e_intern = l_intern+10.
CLEAR d_belnr.
d_belnr = e_intern.
*BSEG - PARTIAL PAYMT/FULL PAYMT WT DISC - Get Total Amount without Bank
*charges
SELECT bukrs belnr gjahr buzei augbl rebzg rebzj sgtxt dmbtr wrbtr
qbshb bschl NEBTR
FROM bseg INTO CORRESPONDING FIELDS OF TABLE t_bseg
WHERE bukrs EQ d_bukrs
AND belnr EQ d_belnr
AND gjahr EQ d_gjahr
AND buzei EQ d_buzei
AND bschl EQ '25'
AND ( koart EQ 'K' OR koart EQ 'D' ).
<--15.07.2005 Rakesh
ENDIF.
-->20.10.2005 By Yogesh.
CLEAR d_dmbtr.
IF sy-subrc = 0.
LOOP AT t_bseg.
d_dmbtr = d_dmbtr + t_bseg-dmbtr - t_bseg-qbshb.
SELECT SINGLE shkzg INTO (shkzg) FROM tbsl
WHERE bschl = t_bseg-bschl.
*BREAK-POINT.
*******prb13052
IF shkzg = 'S'.
d_dmbtr = d_dmbtr + t_bseg-wrbtr - t_bseg-qbshb.
ELSEIF shkzg = 'H'.
d_dmbtr = d_dmbtr - t_bseg-wrbtr - t_bseg-qbshb.
ENDIF.
IF shkzg = 'S'.
d_dmbtr = d_dmbtr + t_bseg-nebtr." - t_bseg-qbshb.
ELSEIF shkzg = 'H'.
if t_bseg-nebtr <> ''.
d_dmbtr = d_dmbtr - t_bseg-nebtr." - t_bseg-qbshb.
else.
d_dmbtr = d_dmbtr - t_bseg-wrbtr." - t_bseg-qbshb.
endif.
ENDIF.
*tables: reguh, payr.
select single * from reguh where zbukr = d_bukrs
and vblnr = d_belnr
and LAUFD+6(4) = d_gjahr.
*select single * from payr where zbukr = d_bukrs
*and vblnr = d_belnr
*and hbkid = reguh-hbkid
*and hktid = reguh-hktid.
*d_dmbtr = payr-rwbtr.
*if d_dmbtr < 0.
*d_dmbtr = d_dmbtr * ( -1 ).
*endif.
CLEAR tab_in-value.
READ TABLE tab_in WITH KEY 'REGUD-SWNES'.
d_DMBTR = tab_in-value.
translate d_dmbtr using '* '.
translate d_dmbtr using ', '.
condense d_dmbtr no-gaps.
d_dmbtr1 = d_dmbtr.
*******prb13052
ENDLOOP.
PERFORM z_conv_amt USING d_dmbtr CHANGING d_amt.
*Pass the Net Amount output to the outgoing table tab_out-name =
*'NETAMT_TOT'.
CLEAR: tab_out-value,tab_out-name.
READ TABLE tab_out WITH KEY 'NETAMT_TOT'.
tab_out-value = d_amt.
" For inserting '*' ahead of value
SHIFT tab_out-value LEFT DELETING LEADING space. """"????IMP
MODIFY tab_out INDEX sy-tabix.
Get the Amount in words for Indian currency
Can also use the FM 'HR_IN_CHG_INR_WRDS'
CALL FUNCTION 'Z_SPELL_AMOUNT_INR'
EXPORTING
amount = d_dmbtr1
IMPORTING
rupees_str = d_words.
Shift left since above Function Module introduces an initial space
SHIFT d_words LEFT DELETING LEADING space.
<-- 21.05.2005
*CALL FUNCTION 'C147_STRING_SPLIT_AT_POSITION'
EXPORTING
i_string = d_words
i_position = 80
IMPORTING
E_HEAD = d_words1
E_TAIL = d_words2.
len = STRLEN( d_words ).
Only 80 characters can be passed to one SAPScript symbol
Split 'd_words' into 'd_words1' and 'd_words2'
since 'DEFINE' in SAPScript displays maximum 80 charact -
Document-based web services - WebLogic 8.1
Hi all,<br>
I'm exposing a stateless session bean method as a web service. The in/out parameters are XML documents so my method signature looks as follows:
<br><br>
public Document collectMessages( Document request )
<br><br>
Accordingly I want to use document-based web services. I use <b>servicegen</b> to create all server-side classes required for the web service.
<br><br>
I'm testing the service from the WebLogic provided test page. For document-based services, the text-area is initially populated with the following content
<br><br>
<pre><!-- Do not know how to create a sample instance for this part due to the following exception:java.lang.InstantiationException: org.w3c.dom.Document. Pls replace this with the correct XML before invoking the service. --->
<['http://www.revenue.ie/webservices/ris/rcm/webservices']:RcmCollectRequest/></pre>
<br><br>
When I invoke the service I get the following error:
<br><br>
<pre><!--RESPONSE.................-->
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<env:Body>
<env:Fault>
<faultcode>Client</faultcode>
<b><faultstring>Unable to find a matching Operation for this remote invocation <RcmCollectRequest>
</RcmCollectRequest>. Please check your operation name. </faultstring></b>
</env:Fault>
</env:Body>
</env:Envelope></pre>
<br><br>
I've searched for this error and seen it in the forum only a number of times. It seems as though some manual manipulation of the web-services.xml document can solve it. Does anyone have an example? My <b>web-services.xml</b> document looks as follows:
<br><br>
<pre><?xml version="1.0" encoding="UTF-8"?>
<web-services>
<web-service useSOAP12="false" targetNamespace="http://www.revenue.ie/webservices/ris/rcm/webservices" name="rcmmessageservices" style="document" uri="/">
<types>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:stns="http://www.revenue.ie/webservices/ris/rcm/webservices" elementFormDefault="qualified" attributeFormDefault="qualified" targetNamespace="http://www.revenue.ie/webservices/ris/rcm/webservices">
<xsd:element type="xsd:anyType" name="RcmCollectRequest" nillable="true">
</xsd:element>
<xsd:element type="xsd:anyType" name="RcmCollectResponse" nillable="true">
</xsd:element>
</xsd:schema>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:stns="java:ie.revenue.rcm.ejb.session" elementFormDefault="qualified" attributeFormDefault="qualified" targetNamespace="java:ie.revenue.rcm.ejb.session">
<xsd:element type="stns:InvalidRequestException" name="InvalidRequestException">
</xsd:element>
<xsd:element type="stns:SystemUnavailableException" name="SystemUnavailableException">
</xsd:element>
<xsd:complexType name="InvalidRequestException">
</xsd:complexType>
<xsd:complexType name="SystemUnavailableException">
</xsd:complexType>
</xsd:schema>
</types>
<type-mapping>
<type-mapping-entry deserializer="weblogic.xml.schema.binding.internal.builtin.DocumentCodec" xmlns:p2="http://www.revenue.ie/webservices/ris/rcm/webservices" type="p2:RcmCollectResponse" serializer="weblogic.xml.schema.binding.internal.builtin.DocumentCodec" class-name="org.w3c.dom.Document">
</type-mapping-entry>
<type-mapping-entry deserializer="ie.revenue.rcm.ejb.session.SystemUnavailableExceptionCodec" xmlns:p3="java:ie.revenue.rcm.ejb.session" type="p3:SystemUnavailableException" serializer="ie.revenue.rcm.ejb.session.SystemUnavailableExceptionCodec" class-name="ie.revenue.rcm.ejb.session.SystemUnavailableException">
</type-mapping-entry>
<type-mapping-entry deserializer="ie.revenue.rcm.ejb.session.InvalidRequestExceptionCodec" xmlns:p4="java:ie.revenue.rcm.ejb.session" type="p4:InvalidRequestException" serializer="ie.revenue.rcm.ejb.session.InvalidRequestExceptionCodec" class-name="ie.revenue.rcm.ejb.session.InvalidRequestException">
</type-mapping-entry>
<type-mapping-entry deserializer="weblogic.xml.schema.binding.internal.builtin.DocumentCodec" xmlns:xsd="http://www.w3.org/2001/XMLSchema" type="xsd:anyType" serializer="weblogic.xml.schema.binding.internal.builtin.DocumentCodec" class-name="org.w3c.dom.Document">
</type-mapping-entry>
<type-mapping-entry deserializer="weblogic.xml.schema.binding.internal.builtin.DocumentCodec" xmlns:p1="http://www.revenue.ie/webservices/ris/rcm/webservices" type="p1:RcmCollectRequest" serializer="weblogic.xml.schema.binding.internal.builtin.DocumentCodec" class-name="org.w3c.dom.Document">
</type-mapping-entry>
</type-mapping>
<components>
<stateless-ejb name="ejbcomp0">
<ejb-link path="rcm-ejb-1.0.jar#CustomerMessageController">
</ejb-link>
</stateless-ejb>
</components>
<operations>
<operation name="collectMessages" method="collectMessages(org.w3c.dom.Document)" component="ejbcomp0">
<params>
<param style="in" xmlns:p1="http://www.revenue.ie/webservices/ris/rcm/webservices" type="p1:RcmCollectRequest" location="body" name="document" class-name="org.w3c.dom.Document">
</param>
<return-param xmlns:p2="http://www.revenue.ie/webservices/ris/rcm/webservices" type="p2:RcmCollectResponse" location="body" name="result" class-name="org.w3c.dom.Document">
</return-param>
<fault xmlns:p3="java:ie.revenue.rcm.ejb.session" type="p3:SystemUnavailableException" class-name="ie.revenue.rcm.ejb.session.SystemUnavailableException" name="SystemUnavailableException">
</fault>
<fault xmlns:p4="java:ie.revenue.rcm.ejb.session" type="p4:InvalidRequestException" class-name="ie.revenue.rcm.ejb.session.InvalidRequestException" name="InvalidRequestException">
</fault>
</params>
</operation>
</operations>
</web-service>
</web-services>
</pre>
<br><br>
Thanks in advance,<br>
EoinHi Eoin,
I had the exact problem. Struggled a lot and still couldn't figure out. I think its a problem in 8.1. Not sure. Might want to check with the support guys. If you are struck with 8.1 and still couldn't figure out, AXIS would be a option for you. Just an FYI. Thats what we are doing now.
Luckily for us we are migrating to 9.1 and I just completed a POC for doc oriented webservices in 9.1. It works like a charm.
Thanks and good luck
- Aspert -
Documentation requested for Program Enrollment
Hi, i enrolled for the iPhone Developer Program, but im stuck in the phase where i have to fax ( +1 (408) 974-1053 ) the enrollmentID and documtations about company.. unfortunately the fax is always busy!
It's whole day im trying to send it, but nothing.
Does exist another fax number?
ps: im from italy.Hi everyone,
I started following the enrollment registration process as an agency developer. Then I received this mail from Apple which says to send them the documentation needed for my program enrollment, adding this last point in the end of the mail:
"If we do not receive your information within the next seven (7) days, we will assume you are no longer interested in continuing your enrollment and will withdraw your request."
Unfortunately more then 7 days passed by. In fact I see right now in my Program Summary section that my Developer Program Status shows a yellow triangle icon with a red written line:
"Enrollment Pending"
I don't know the exact meaning of that.
Does it mean my registion has been quitted? So do I have to enroll with a new Apple Developer profile, with new e-mail and new password?
One more thing.
I didn't send yet documents requested, so should i send them holding this first account or should I enroll with a new one then send all documents needed?
Thanks a lot!
MF
Maybe you are looking for
-
Double Click on ALV Report Output, Bringing to selections creen
Hello Gurus, Please help me When i do double click on ALV Report output , it is going back to Selection screen, actually its working as Back button. Now how to stop it.. I did debugging but i cannot trace it.
-
Hi All, I want A T-Code Through which I can see all the users who has created the po in a particular month?
-
Error in Customer down payment clearing
Hello Friends, I am trying to clear the customer down payment through transaction f-39. We have also created one validation rule that reference 3 field is mandatory so i am getting error that reference field is mandatory. But reference field becomes
-
Workflow, Folios and Document Update question?
" Hi All, System Setup - Oracle UCM 10gR3, ORacle 11G DB using OracleText We are currently passing a folio through the workflow and want to be able to read the metadata of the content/docuemnt item stored in the folio. We can do this from iDoc from s
-
Hi Guys, i'm running Messaging 7u4-23.01(7.0.4.23.0) 64bit on Solaris SPARC and as described in the subject i need to forward all messages (incoming and outgoing) of a single user to a different email account. I tried with a filter like this in mailS