Payroll Documents.
Hi Experts.
I am new to USA Payroll, I have the PDF documents, I need to learn on the system i.e scenario's or call it exercises. Can anybody forward me that kind of stuff. I need to learn the configuration besed practices.
Any Help will be truely Appreciated.
Regards,
Venkat.
Hi Frnds ,
Can u pls. forward me the US payroll Docs on my [email protected] id .
As i am totally new in US payroll , & recently i have work in the same .
Thanks in Advance .
pooja
Similar Messages
-
Can anybody send me document about the payroll scripts and forms.
Advance thanks
Edited by: Zsolt Markus on Jan 21, 2008 11:21 AMhttp://help.sap.com/saphelp_nw04/helpdata/en/a5/de6838abce021ae10000009b38f842/frameset.htm
check this one and let me know if there is anyhting else
thanks
sikindar -
Posting Error - While Posting Payroll
Hi Gurus,
While posting payroll document, system is asking for GL Account, but when we assign HR Clearing Account in "Assign Technical Accounts", then system gives error that business area is missing line item 001 because document splitting is activated in FI.
But ideally should not ask for the GL Account.
Please tell me how can we solve theHello Laxmi Narayan,
Compare the payroll cluster with wage type mentioned in posting run... normally this type of error comes when infotype 9 i.e. Bank Details are not maintained etc.
If helpful please award points
Parag -
GL account with line items in line type 'S' document split?
Hi Experts,
We found in PCP0 there are payroll documents which has GL account with with line items in line type 'S' document split. Unlike other line items with line type 'blank' these line items cannot be opened and display the wage type details. How can we know from which wage type these line items were created?
Regards,
AllanThese line items are caused by company transfer and they are cleared by themselves between companies.
-
Hello All.
I have a problem when post a payroll documents and a vendor document split is generated.
The problem is that the technical account isn't cleared between both documents.
In the first document (document with balance accounts) the technical account could have 0.01less than the second document (vendor document). Example: 1525.26 in balance document and -1525.27 in vendor document.
Each one are cleared, but not between them.
One more think, this happen in the local currency in FI document.
I mean, in HR everything are OK, the technical account have the right amount between documents in company currency (PEN)
But when I see documets in FI system (tx: FB03), the amount in document (PEN) currency is OK, but the amount in local currency (USD) is not equal between both documents, it has 0.01 of difference....
Please let me know if I explain well the problem and what do you think it could be?
Thanks in advance
Enrique VeraHi,
Check the vendor master data in XK02. In payment transactions under company code data check "Individual payment" check box may be flagged.
If this happens , multiple documents will be generated while postings. untick the checkbox and try with new postings. This may solve your problem.
contact your FI resource to resolve this....
Thanks & Regards,
Y.V.P.Deepak -
Documents types definition rational
Dear All,
What i expect from you all is not the "How to do" but the "Why doing that this way"
We are designing our customer system and i have been asked the following questions:
Why should we use these document types?
What is the rational of creating new ones?
I tried to find out the solution for my question over the WEB but I have not been able to resolve my issue.
AB General document
DG Customer credit memo
DZ Customer payment
DR Customer invoice
KZ Vendor payment
KG Vendor credit memo
KN Vendor net invoice and credit memo
KR Vendor invoice
SA All G/L accounts
What is the rational to choose the number of documents types to be used?
Thank you in advance for your help
Kind regards
M.Hi
Why should we use these document types ?
As already explained by MBN and Sowmya we use the different doc types
1.To differentiate the transactions posted in FI from different modules and in FI module itself.
2.To build the logic as per user requirement in respect of any particular document type
3.To identify the transactions posted from a particular module or from the same module(ex., for cash transactions we can have CJ)
4.Better not to have same document type for two types of postings ex., for postings from payroll doc type AB and for clearing document also doc type AB since differentiation between payroll documents and clearing documents becomes difficult.
Rational of creating a new one
1.To identify the nature of transactions pertaining to one particular area viz., excise etc.,we can have a new document type for example Doc Type EX
What is the rational to choose the number of documents types to be used?
Discuss with the client and decide.
In general for customers we use doc types beginning with letter D and for Vendors we use doc types beginning with letter K and for GL documents we use SA.
Regds -
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 -
Generating Payable document at the time of Salary Loan,Advance booking
Dear All,
Our client required when Salary Loan will book through the Payroll same time system will generate Payroll document and f i Person will check this doucment and he will pay the loan amount is it possiable in Payroll?
Balwant.for this we have implemented travel management module
BMS -
U.S. Payroll docouments
Hi Lincoln,
Can u pls send me the U.S. Payroll Documents.
RituHi,
Please check the document on Payroll US.
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PYUS/PYUS.pdf
Reward if helpful,
Thanks,
Preetham. -
Posting Loan to Vendor Employee
Dear Experts,
We're in 4.7. We have a requirement where we need to keep track of loan payment of all our individual employees. Is it possible to post the loan payment in payroll individually to each and every corresponding vendor employees ? Any input will surely be appreciated.
Thanks and regards,
AriefHi
You can do the following.
1.Define your employees as vendors and attach the employee code to respective vendor.
2.Define Symbolic Accounts
In this step, you create the symbolic accounts that you require for posting to Accounting.
A symbolic account has the following characteristics:
A four-character alphanumberic code
A descriptive text
An account assignment type (AA type). This defines the type of posting (posting to expense account, posting to payables account, and so on) that applies to the wage types that are posted to the symbolic account.
An employee grouping for account determination (EG) indicator
The following table shows what kind of account and what transaction is linked to an account determination type and what additional information (for example, for cost assignment) is also included in the posting transaction.
AA type Meaning Transaction Additional fields
C posting to expense account HRC cost assignment
CN posting to expense account HRC cost assignment
without quantity without quantity
R posting to expense account HRC
if accounting is installed in
R/2 System.
F posting to bal. sheet account HRF
FL posting to bal.sheet account HRF
for checking balance
in retroactive accounting
(recalculation difference account)
FO posting to bal. sheet account HRF
(original periods for
wage types whose amount
cannot change
retroactively)
Q posting to bal. sheet account HRF personnel number
with personnel number
D posting to personal HRD acc. determination
customer accounts with personnel number
DF posting to fixed customer HRD direct assignment
of customer account
L posting to customer HRD acc. determination
account(for specific loan) with personnel number
loan type,
sequential number
K posting to personal vendor accounts HRK acc. determination with
personnel number
KF posting to fixed vendor HRK direct assignment
acc. of vendor account
Note the following with regard to account assignment types:
In the standard system, no quantities are transferred from wage types in the payroll result to the payroll documents and the resulting accounting documents, although information on quantities is available on the report log for report RPCIPE00 (or RPCIPX00). It is also possible to modify the system to access this information. The account assignment type CN is only useful if you have made this modification and if, in certain instances, you want to suppress the transfer of quantity information.
The account assignment types FL und FO are only of use if there are cross-company code transactions. For more information on customizing cross-company code transactions, refer to Posting to Company Code Clearing Accounts.
We recommend that for symbolic accounts with account type FO, you determine the account in Accounting independent of the Employee grouping for account determination (Feature PPMOD). For this reason, only one G/L account is provided for the payment of wages and salaries as standard. If you determine this G/L account depending on the employee grouping for the account determination, this can lead to inconsistencies when posting the retroactive accounting results. This is due to the fact that when posting retroactive accounting results for wage types that cannot change retroactively, a technical posting takes place (for example, for the wage type Payments (/559)). Since this technical posting usually takes place in the same account in Accounting, it balances to zero and does not appear in the posting document. However, if you determine this account independently of the employee grouping for account determination, and an employee falls in a different employee grouping due to a retroactive change in the HR master data or feature PPMOD, the technical posting cannot balance to zero because two accounts are affected in Accounting. This is why you have to make changes manually in this case.
Example
The wage types Basic pay and Overtime both represent personnel costs and should therefore be posted to expense accounts. You also want to assign these wage type amounts to Cost Accounting objects. Both wage types are dealt with in the same way as far as posting is concerned and can therefore be posted to the same symbolic account. You must specify the account assignment type C, since, in Accounting, there should be a posting to expense accounts and Cost Accounting should be provided with information.
Requirements
You have carried out the step Define Employee Grouping for Account Determination
Standard settings
Symbolic accounts are already set up in the standard system. In this step, you can modify these to meet your requirements.
Recommendation
We recommend that you do not change the definition of the symbolic accounts. If changes to the definition of the symbolic accounts are necessary, you should map the changes using new symbolic accounts.
Activities
1. Check that the existing symbolic accounts meet your requirements. Note the EG indicator. If this indicator is set for an account, posting to this account also considers employee grouping for account determination. With the exception of the key (column SymAcc), you can change the default values.
2. To create additional symbolic accounts, choose New entries
3. To delete unnecessary symbolic accounts, mark the account and choose Edit -> Delete.
Further notes
Symbolic accounts are not country-specific.
3.Assign Vendor Accounts
In this step, you make the settings required for posting to vendor accounts.
There are two kinds of vendor accounts available:
Fixed vendor accounts: Employee grouping for account determination offers the most precise means of control for posting to fixed vendor accounts.
Employee vendor accounts: Posting to employee vendor accounts enables posting for a specific personnel number.
In this step, you make entries in table T030 for the assignment of vendor accounts to symbolic accounts.
Example
Fixed vendor account
You want to deduct dues to various unions from the employees in your enterprise. For each union, you have set up a specific wage type for dues and a specific symbolic account. In this step, you assign a fixed vendor account to each of these symbolic accounts.
Employee vendor account
You want to post dues to a different vendor account for each employee. To this effect, you have created a symbolic account for all employees. In this step, you specify how the corresponding employee vendor accounts are determined.
Requirements
You have created the required vendor accounts in Financial Accounting.
You have carried out the step Define Symbolic Accounts. In that step, you created symbolic accounts with the relevant account assignment types (KF for fixed vendor accounts, K for personal vendor accounts). In that same step, you flagged the indicator EG-depend for symbolic accounts to which you want to post in line with the Employee grouping for account determination.
If you want to post to employee vendor accounts, you have entered the relevant personnel number in one of the following fields in the vendor master data of Financial Accounting. We recommend that you use the Personnel number field. If you use another field, you must enter the personnel number with leading zeros.
Personnel number
Search term
Telephone 2
Data line
Teletext number
Standard settings
There are no standard settings for posting to vendor accounts. If, in the step Define Symbolic Accounts, you have not created any symbolic accounts with the account types KF or K, you do not have to carry out the step Assign Vendor Accounts.
Activities
1. Enter the required chart of accounts.
2. To make settings for the posting procedure Personnel posting to vendors (HRK), choose Rules
3. Choose Posting key. Enter the posting key for postings to vendor accounts or copy the default values (21 for debit posting and 31 for credit postings).
4. Choose Accounts. Make the corresponding entries in the table T030.
a) If you want to assign a fixed vendor account to a symbolic account, and if required, an employee grouping, enter the number of the vendor account in the Acco column.
b) If you want to assign an employee vendor account to a symbolic account, and, if required a employee grouping, enter the relevant key (see table below) in the Acco column.
Personnel number in field (Vendor master data) Entry in the Account column (T030)
Personnel number *0002
Search term *0001
Telephone 2 *0003
Data line *0004
Teletext number *0005
Further notes
It is not possible to use the special G/L indicator with posting to customer accounts.
in summary whatyou do is defne a symbolic account of type K , link your wage type to this sym account , define the posting to vendor with *0002
regards
Pravin -
FI/CO Posting - Business Area Problem
Hi all,
I am running PC00_M99_CIPE program.
Business areas seem to accurate that consisting of payroll document . But business areas is all the same within the FI document.
What causes this problem? (user-exit? customizing? OSS-Note?)
Can you help me please.
Best Regards.Sir,
Wat is the Sap FI Procedure for Transfer Posting of Costs booke from one BA to another
eg. Suppose while doing any transaction business area 4500 should be picked but instead of 4500 business area 7000 is being assigend which is wrong the correct busines area should be 4500. so it is not possible all the time to reverse the enter so wat is the procedure to assign the correct businee Area
Suppose the transaction like Payment Posting Excise Cenvat Posting etc..
So please suggest
Urgent Help required
Juhi -
Small window changes in line printer
We are using a line printer EPSON FX-980. We are using sapscripts to print.
We are printing in a not so flexible format. We have the formats already pre-printed and we need to make small changes to adjust the output.
Almost everything is alright, except some variables that cross some pre-printed lines.
We only need to move a window aprox. 1mm down to adjust the exit.
However, when we try to make small changes, the windows jumps a whole line, not like laser printer that adjust to fractions.
For example, my problematic windows is in 28 ln. No matter if I change it to 28,01 or 28,5, the widow jumps to 29ln.
I tough it was the printer couldn't print small details, but I drew several lines with small spaces between in ms paint and it prints them fine. So I'm guessing is the driver.
I already used the two drivers for line printers, also changed the device type line lenght and nothing has been resolved.
Is there a way to do this?hi,
Modifying the SWIN (SAPWIN) Device Type
The SWIN device type allows you to use any printer or fax that the Microsoft Windows Print Manager can use, regardless of whether the SAP R/3 System has a device type for the corresponding device. In this case, it is actually the Microsoft Windows Print Manager and Windows driver that format a document and make an output-ready data stream out of it.
Modifying SWIN is a little different than working on other device types because SWIN does not deliver an output-ready data stream. Rather, it converts the internal SAP R/3 document format into a special SAP R/3 formatting language. The SAPSprint service understands this formatting language. SAPSprint, in turn, converts the SAP R/3 formatting commands into Microsoft Windows GDI commands, which the Print Manager and the Microsoft Windows device driver can use for preparing print-ready output data.
The upshot: rather than modifying printer commands in actions and print controls, in SWIN you need to work with SAP R/3 formatting commands. The SWIN formatting language is documented in this section.
SWIN Device Format Actions
With SAPscript formats, SWIN does not use the Printer initialization or Reset actions. Enter a comment line -- # Not used -- in these two actions in the SAPscript device formats in your copy of SWIN. This ensures that the actions will be ignored when they are called during output. SWIN list formats do use the Printer initialization and Reset actions.
In your copy of SWIN, insert commands only in the device type format actions that the SAP R/3 standard device type SWIN uses.
Frequently Made Changes to SWIN
● Adjusting the position of output on the paper.
In a SAPscript form definition, positioning information refers to the absolute dimensions of the paper to be used for outputting the form. However, the position information in SAPscript forms is added to the coordinates system of the target output device during execution to determine where the form objects are to appear on the output page.
Since output devices use different origins for their coordinate systems, this means that SAPscript and the spool system must offer a way to adjust form positionings to reflect the coordinate system used by an output device.
You can adapt your forms to the differing coordinate systems of output devices in the device definition, where individual printers and fax machines are made known to the SAP R/3 spool system.
Set the fields: Choose Tools ® CCMS ® Spool ® Spool Administration, change the corresponding output device, and switch to the Output Attributes tab page. There, you can set the horizontal positioning in Horizontal move, the vertical positioning in Vertical shift. Positive values (> 0) move the output down or to the right. Negative values in the format xxx move the output up or to the left. No decimal values are permitted. For fine positioning, use MM (millimeters) or PT (points, 10 points / inch).
If a window in a form definition is to appear 1 cm from the left edge of the paper, the window will actually be printed 1.5 cm from the left edge of the paper on a Hewlett-Packard LaserJet printer. The LaserJet starts its X-axis coordinate system 0.5 centimeter from the left edge of the paper. On a PostScript printer, on the other hand, the window will start 1 cm from the left edge of the paper, because PostScript uses the physical boundaries of the paper for its coordinate system.
You can adjust the positioning of the output on the HPLJ4 (LaserJet) printer by entering -5 MM in the Horizontal move field in the second screen of the device definition of each HPLJ4 printer.
● Setting Basic List Print Properties: Character pitch, line leading, type size.
To make these adjustments, you need to change the Printer initialization action in the X_ formats in your copy of the SWIN device type.
There, you can adjust the character pitch (character spacing), leading (line spacing), and type size with the following commands:
Property
SWIN Formatting Command to Use
Character pitch
ec is the type size in twips (20 twips = 1 point).
For example: eS200X sets the type size to 10 points (200 twips / 20 = 10 points).
The SWIN data stream protocol is an internal SAP R/3 format that may change without prior notice. SAP intends to make only upwardly compatible changes to the SWIN protocol. That means that you should always be able to use the newest version of SAPSPrint, even if you have not upgraded your SAP R/3 System itself.
SAP guarantees, however, only that the SWIN device type will function correctly with the development level of the SAPSPrint transfer program that is specified for a particular SAP R/3 Release.
SAP Printing Guide (BC-CCM-PRN)
Implementation considerations
The SAP Printing Guide describes the functions of the SAP Spool System. This system was designed to be used on various platforms. SAP provides its own spool service and a spool database so that users do not have to deal with operating system-specific issues.
The platform-independent SAP spool system is responsible for the output of forms and documents. The data to be printed is first temporarily stored (spooled), then formatted, and finally transferred to a host spool system to be output. You can control all of your output from the SAP System and do not need to arrange further processing in the host spool system.
The following are among the main tasks of the SAP spool system:
· Processing and managing print requests
· Administering output devices
· Technical mapping of the output devices in the SAP System
Features
Among other things, the SAP Printing Guide describes the following:
· Print Process in General
An introduction for users and administrators, in which the print process from document to printout is explained in general.
The focus of the introductory sections is the Output Controller (transaction SP01), which can be used by both administrators and users to manage print requests.
· Spool Access Authorizations
This sections and its subsections describe the access authorizations required specifically for the spool system.
· Possible Print Architecture and Print Methods
The various print architectures are described in this section and its subsections, that is, the different constellations of hardware and software components with the corresponding access methods: Each architecture also requires a specific print method, such as:
· Local printing: The spool server (application server with a spool work process) and host spool system (operating system spooler) are on the same host.
· Remote printing: The spool server and the host spool system are on different hosts.
· Frontend printing: Print data are to be printed on the default printer of the users PC.
· Printing using SAP GUI for HTML
· Output Devices in the SAP Spool System
Output devices must be defined in the SAP System so that they can be addressed from the SAP System.
You do this using device definitions with which the devices are managed in the SAP System.
This link takes you to a description of these device definitions and their printer settings.
· Spool Server
This section explains what a spool server is, how you define it, and what using logical servers and alternative servers involves.
· Device Types for SAP Output Devices
Device types are explained in this section. A device type in the SAP system is the category of printer to be addressed. The information in the device type, such as font selection, page size, and character set selection is used to convert a document from the internal SAP format to a device-specific, printable data stream.
· Connecting to an External Output Management System (OMS)
This section explains how you can connect the SAP spool system to an external Output Management System.
· Maintaining the Spool Database
This link takes you to a section explaining how you maintain your spool database to ensure optimal performance.
· TemSe Database Storage
This section and its subsections explain what TemSe is and how you can manage TemSe objects.
· Analyzing Printing Problems
This link takes you to examples that will provide you with support in identifying and correcting errors
Printing from the SAP System
Features
Using the SAP output system, you can output many types of documents on output devices such as printers or fax machines: purchase orders, invoices, delivery note, payroll documents, e-mails, report lists, and so on.
Process Flow
Unlike most other programs, which forward print requests directly to the printer, the SAP System temporarily stores the print data. If you want to print data in an SAP System (online or in the background) and choose a print function, such as , the SAP output system creates two types of print requests:
1. a spool request, which temporarily stores the data to be printed in the system
2. an output request, which sends the data to the desired output device
If you want your document to be printed immediately on your printer without temporary storage, you must have made a setting in the print window for immediate output. In this case, the spool request and output request are generated immediately, and the data is printed.
If you want to temporarily store the data, do not choose print out immediately. You can display the temporarily stored print request (spool request) in the output controller and/or print it at a later time
thanks
karthik -
ABAPer looking for basic knowledge on SAP FI
Hi,
I got in to ABAP recently. I would like learn basis of SAP FI. if any one have any info regarding the same.pls share.
Regards,
Shrini..hi,
Introduction
The SAP FI Module has the capability of meeting all the accounting and financial needs of an organization. It is within this module that Financial Managers as well as other Managers within your business can review the financial position of the company in real time as compared to legacy systems which often times require overnight updates before financial statements can be generated and run for management review.
The real-time functionality of the SAP modules allows for better decision making and strategic planning. The FI (Financial Accounting) Module integrates with other SAP Modules such as MM (Materials Management), PP (Production Planning), SD(Sales and Distribution), PM (Plant Maintenance),and PS (Project Systems).
The FI Module also integrates with HR(Human Resources) which includes PM(Personnel Management), Time Management, Travel Management, Payroll.Document transactions occurring within the specific modules generate account postings via account determination tables.
The FI (Financial Accounting) Module components.
The FI Module comprises several sub-modules as follows:
Accounts Receivables
Accounts Payable
Asset Accounting
Bank Accounting
Consolidation
Funds Management
General Ledger
Special Purpose Ledger
Travel Management
Accounts Receivables records all account postings generated as a result of Customer sales activity.
These postings are automatically updated in the General Ledger . It is within the Accounts
Receivables Module that you can monitor aging of the receivables and generate customer analysis. The Accounts Receivable Module also integrates with the General ledger, Sales and Distribution, and Cash Management Modules.
Accounts Payable records account postings generated as a result of Vendor purchasing activity. Automatic postings are generated in the General Ledger as well. Payment programs within SAP enables the payment of payable documents by check, EDI, or transfers.
Asset Accounting is utilized for managing your companys Fixed Assets. SAP allows you to categorize assets and to set values for depreciation calculations in each asset class.
Bank Accounting allows for management of bank transactions in the system including cash management.
Consolidation enables the combining of financial statements for multiple entities within an organization. These statements provide an overview of the financial position of the company as a whole.
Funds Management allows management to set budgets for revenues and expenses within your company as well as track these to the area of responsibility.
General Ledger is fully integrated with the other SAP Modules. It is within the General Ledger that all accounting postings are recorded. These postings are displayed in real-time providing up-to-date visibility of the financial accounts.
Special Purpose Ledger is used to define ledgers for reporting purposes. Data can be gathered from internal and external applications.
Travel Management provides management of all travel activities including booking trips and handling of expenses associated with travel.
for further details refer to this link...
http://www.thespot4sap.com/IntroTo/SAP_FI_Module_Introduction.asp
http://help.sap.com/saphelp_nw04/helpdata/en/f5/b3dcaf994a11d1b54f0000e835341d/frameset.htm
more links in,
SAP FI Concepts...
Regards,
Arunsri -
Server got hang while doing FI posting
Hi experts
While POSTING THE PAYROLL DOCUMENT (scheduled as a background job in SAP PRDN server), the server got hanged due to some hardware issue and had to switch off.
Now in PCP0, the run status of the document is shown as "Documents posted", but no entries have been made in FI module for this payroll document.
We tried to reverse the document, but is it creating "incorrect reversal document".
Kindly advise us what should we do now.
Thanks in advance.Hi,
if posting has happened incorrectly and values are not in the tables then do this
find the document that is posted with the status indicator 50. if you dont find it set the filter and find it then check the check box of
that document the reverse it.
another way if the document is posted then please check the GL accounts amount that is posted. if you dont find any amounts are posted then you can with new postings to FI.
all the best
regards,
mohammed -
User Exit for FI automatic posting
My system has some customised fields in the bseg table for additional CO Dimension. User exit has been used to validate these fields when entering in FB01. However, there is an issue when it comes to automatic posting such as Asset Depreciation and Payroll Documents. Anyone aware of which user exit could be used to validate this kinda automatic posting?
Hi,
As you are telling it is for FB01, one thing you have to observe..some transactions only comes under the FB01 category like, f-43, f-02, f-22, and some of them. If you see the header details of the documents like these, you can identify them with the FB01 as the TCODE and in case of the FB60, FB70, FB50 documents posted with these tcodes will have the TCODE as FB50, FB60, FB70.
So, in your case the transactions are not relevant with the FB01, check in that way.
for finding user exit you can get them using the TCODE : CMOD / SMOD using the specific function groups in which the tcodes falls.
VVR
Maybe you are looking for
-
Mountain Lion Email doesn't work even with 10.8.1 update!
My mail application completely failed shortly after the upgrade to Mountain Lion. None of the user advice has repaired it from these forums, so I have now resigned myself to using my ipad and iphone to conduct all my business emails. I was hopeful th
-
My multi-state object disappear's when I export to PDF but works in Preview mode?
I created a multi-state object which is a series of logos that appear when a button is clicked. There are two buttons one is set to go the the previous state and one is set to go to the next state. When I view it in the preview mode it works fine but
-
Syncing photos between devices
I use an iPhone 5s with os 7.1.2 and just got iPad air 2 with os 8.1. Why can't I see my old iPhone pictures on my iPad? There is nothing on photo stream and nothing on iCloud library beta when I turn it on
-
2nd Broken mini in one year.
My first 4 gb mini's(bought in sept.) battery was broken and only lasted about 20 min. and then they mailed me another one, which i got in May and now that one is broken and has been broken for about a month now(the battery again). Im wondering if i
-
Camera disappeared When updating to ios5
After updating My iPad model MB293KS to ios5.1.1 the camera disappeared is there à way to find it? Or Should I try to reinstall the system?