Monday, September 29, 2008
Friday, September 26, 2008
RSMIPROACT: The SMI background report which is used to select the stock and requirement data and generate the IDoc.
RSNAST00: The creation and sending of PODs are done.
RSEOUT00: Selects and sends the IDocs with the status 'to be processed' and send them to the target system.
Thursday, September 25, 2008
Activate Settings in Order Document Management
In this IMG activity, you can activate the following settings:
For the activation, you convert the inactive settings to the active settings. Order document management (ODM) only uses the active settings.
The system monitors the inactive settings when activation takes place and, if necessary, generates ABAP Dictionary objects (structures and tables).
If the activation does not run without errors, you can call generation. You have to run activation again once generation has been completed successfully.
Wednesday, September 24, 2008
You need to
1. in IMG->Advanced Planning and Optimization->Supply Chain Planning->Supply Network Planning (SNP)->Configure Transfer to OLTP Systems or /n/SAPAPO/SDP110
. change the setting from periodic transfer to immediate transfer based on your application.
2. However, if in /SAPAPO/C4 - Maintenance of global parameters , you change the setting of Recording (Default/Collect Changes/Do not collect changes), it will overwrite the settings you've made in 1.
Do not collect changes in 2 equals immediate transfer in 1.
If you select periodic transfer in 1, or collect changes in 2, you need to go to Process Change Pointers to manually process the transfer, Tcode: /SAPAPO/C5 - Send Planning Results to OLTP
3. If you are using CTM, check in the /n/SAPAPO/CTM, Settings tab, R/3 Integration, if Transfer Mode has been set to transfer or not transfer.
4. Also check /SAPAPO/CP1 - Maintenance of Distribution Criteria. If you want to transfer PREQ from APO to ECC as PIR, you need to Planned Independent Requirement, Location, Logical system and System ID as an entry.
If the External procurement has been register and assigned to appropriate logical system.
When you transfer the Purchase Requisition from APO to ECC. It didn't go through, in the Queue monitor there's a error message saying that the Item Category is not allowed for Document Type ZTP.
Then check the document type setting (IMG->Materials Management->Purchasing ® Define Default Values for Document Type) in ECC and found out that the default setting for Purchase Requsition in ZTP. ZTP is not a standard document type for Purchase Requisition, and it is not recognized in APO. Now I changed it to from ZTP to NB (standard document type for Purchase Requisition). Then the transfer of the Purrqs from APO to ECC go through successfully.
The RFC link between R/3 and APO is a .normal. RFC link. The exchange
of data takes place without using IDocs.
The corresponding Customizing settings in the R/3 are under: Web
Application Server → Application Link Enabling (ALE) (R/3 transaction
SALE), and for APO, similarly, under APO Customizing: R/3 Basis
Customizing → Application Link Enabling (ALE) (APO transaction SALE).
Define RFC Destinations
The RFC links run in both systems under the title .R/3 links.; as far as the
basis is concerned, an SAPAPO System is identical to a R/3 Enterprise.
The User specified in the RFC link should be a .normal. dialog user
(officially recommended and supported by SAP; the dialog abilities of the
user are necessary for the APO-ATP integration in an R/3 sales order).
The authorization profile SAP_ALL should be assigned to the user (in
other words, there is no special authorization profile for this user). Logon
usually takes place in the language that is specified in the RFC connection
(also for the ATP check).
For RFC links, if a transfer error occurs due to network errors you can set
new transfer attempts to start automatically in the definition of RFC link
under Destination → TRFC Destinations.
Determining Target System and Maintaining APO Release
Specifying the SAP APO target system in the settings of the CIF (R/3
transaction CFC1) means that the relevant SAP R/3 Enterprise is
recognized as an SAP APO System. This entry and the maintenance of the
APO release are required for a successful CIF data transfer. The operation
mode behind the system is not maintained manually, but is assigned by
The APO Release must be known to the system, as some points in the logic
of the CIF transfer changed between APO Release 2.0 and 3.0/3.1, for
example, the transfer of PPMs.
Several SAP APO target systems can be specified for integrating an R/3
Enterprise with several SAP APO Systems. In the integration model for
the data transfer from R/3 to APO, the relevant target system is clearly
The target system for the retransfer of planning results from APO
is determined in APO according to publication type, for example,
external procurement or in-house production, and location under APO
Customizing: Advanced Planner and Optimizer (APO) → Basis Settings →
Integration → Publication → Maintain Distribution Definition. The retransfer
is set in transaction /SAPAPO/C4: Tools → APO Administration →
Integration → Settings → User Settings. For SNP planning results, SNP
Customizing defines how the retransfer is to take place.
Hint: Some settings (SM59 and CFC1) can also be called up
centrally in the R/3, using the CIF Menu. You can access the
CIF Menu using the transaction CIF with /n, after you leave the
Easy Access Menu. However, note that new transactions are not
included in the CIF menu. It is also possible to use the Easy Access
Business System Group (1)
Each system must be assigned to a BSG; at least one is necessary in every
case. If there is not a risk of ambiguity, all systems are assigned to the
This and the following presentations show that one SAP APO System is
connected to several R/3 Enterprises, where the same material number
indicates different materials in different systems.
The opposite of this, where the same material has different material
numbers in different R/3 Enterprises, is discussed in the appendix.
Business System Group (2)
The SAP APO System is also to be assigned to a BSG. Development
recommend that you assign the APO System to the BSG, then the data
does not need to be renamed.
Business System Group (3)
For the resources, a BADI, a new technology, is used instead of a customer
Renaming PPMs is usually not necessary: The product number linked to
the PPMs is renamed. The PPMs in theAPO System are then also uniquely
Business System Group (4)
The original R/3 names of, for example, an APO product or location, are
apparent in APO: They are specified in the product or location master as
an external material number or location. This information can be found in
the APO tables /SAPAPO/MATMAP and /SAPAPO/LOCMAP can be
displayed with APO transaction SE16.
Outbound and Inbound Queues
Since PI2001.2, there is an option available where you can choose between
outbound and inbound queues in integration. Previously, you could only
process through outbound queues, which will be the standard case for
this course too, at first.
Monitoring and error handling differentiate slightly for outbound and
inbound queues. These are the only differences for this setting in the
Tuesday, September 23, 2008
Monday, September 22, 2008
Checklist for Setting Up the System Infrastructure
The following table shows the Customizing steps required for the technical integration via Core Interface (CIF).
If you work with SAP R/3 4.0B or higher, an Implementation Guide (IMG) is available for CIF Customizing in the ERP System. There is also an IMG for CIF Customizing in the SCM System. You find the relevant IMG activities in the corresponding IMG under the structure nodes Basic Settings for Creating the System Landscape and Basic Settings for Data Transfer.
CIF Customizing in the ERP System
Check ALE settings and activate, as required:
● Define the logical system
● Assign logical system to client
| || |
Define the RFC destination
If you set the Inbound Queue queue type in the ERP system, you have to register CIF queues (CF*) in the QIN scheduler in the SCM system.
Maintain SCM release
Set number ranges for parallelization
Register CIF queues in the QIN scheduler if you have changed to inbound queues in the SCM system
CIF Customizing in the SCM System
Check ALE settings
● Define the logical system
● Assign logical system to client
| || |
Define the RFC destination
Maintain business system group
Assign Logical System to Business System group
SNSCLNT001 to BSG_01
If you set the Inbound Queue queue type in the SCM system, you have to register CIF queues (CF*) in the QIN scheduler in the ERP system.
Register CIF queues in the QIN scheduler if you have changed to inbound queues in the ERP system
Register CIF queues in the QOUT scheduler, if you have configured outbound queues in the ERP system
Maintain distribution definitions
Create customer exits for uniquely identifying master data. For more information, see the Implementation Guide (IMG) for SCM Basis.
CMOD (Customer Exits)
SE19 (Business Add-Ins)
But prerequisite is that the External Procurement Relationship has to be created and CIFed from ECC to APO.
There are three types of External Procurement Relationships: Purchasing info records, Contracts and Schedule Agreements. They can be checked in /SAPAPO/PWBSRC1.
The conversion can be Mass conversion /SAPAPO/RRP7, or it can be converted individually by setup the Conversion Indicator and double click the order in Product view - /SAPAPO/RRP3.
Check the transfer setting in /SAPAPO/SDP110, if it's the periodic transfer, then you have to use the Process Change Pointer /SAPAPO/C5 to manually transfer to ERP system.
Wednesday, September 17, 2008
PO is normal where you issue the PO to a vendor and expect the delivery. The PO is termed completed when the vendor has delivered the PO quantity or when you have preclosed the PO when the vendor has delivered partial quantity and he has agreed not to send anymore with ref to the PO.
Outline Agreement can be of 2 types:- Contract and SA.
Contract is where you have a contract with the vendor, may be a for a predetermined quantity or predefined value. So everytime you need the matl, you need to make PO ref the contract asking for the delivery of the matl. In such instance when PO is ref with contract its called contract release orders or call off orders.
Scheduling agreement is a long term purchase agreement, where you will keep issuing the delivery schedules whenever there is a change in requirement or at predetermined time intervals. The delivery schedule can be on hour/daily/weekly/monthly basis. But it will contain different zones viz. firm/tradeoff/Forecast. Firm zone schedules are confirmed requirement and need to be taken by ordered party. Tradeoff zone requirement is to purchase the raw materails and ordering party is liable to pay raw material cost, in case of requirement cancellation. Forecast zone requirement is to help the vendor to plan his requirements.
SA is also an agreement with the vendor for the supply of matl, may be a quanity or value. The delivery dates will be maintained in ME38 ref the SA which are called delivery schedules.So you can maintain the delivery schedule and communicate the vendor on Forecase basis or JIT basis. And when you need some more matl then will only create SA deliveries using ME38. SA could be of 2 types:- without release documentation-system will transmit the delivery info to the vendor once you save the document.
With release documentation- after creating the delivery schedules you need to create SA release using ME84.
The main difference between contract and SA is volume of docs generated would be higher in contract since everytime you need to make a PO ref the contract and its time consuming, whereas SA can be integrated with MRP such that it automatically creates delivery schedules during MRP run provided if there is a requirement to the matl.
Tuesday, September 16, 2008
The application log can be accessed using transaction SLG1, or under the following menu path: Supply Network Collaboration -> Tools -> Application Logs -> Display Application Logs.
In the SAP system, you find a set of tools for displaying detailed information on user sessions, work processes, and on the servers in your SAP system.
If you want to work with these tools, choose the path Administration ® System Administration on the initial SAP screen, or run transaction S002. The initial screen for system administration appears. The tools are available under Administration and Monitor.
There are also programs that you can use at operating system level to monitor the message server or the gateway.
The information in this section relates to analyzing the system status. For information about centrally monitoring a system landscape, see the Monitoring section.
Perform the following tasks when monitoring your systems and analyzing problems:
The Application Server Overview (transaction SM51) shows the application servers logged on at the SAP message server. Only these application servers are active in an SAP system.
You can also administer the application servers, and manage and display the status of the users and work processes in all application servers belonging to the SAP system.
If the messages server stops working, it must be restarted as quickly as possible, to ensure system continues to operate trouble-free.
This link leads to information about how to monitor, test, and administer the message server.
The Process Overview (transaction SM50) displays the current status of the work processes on the application server where you are logged on.
The process overview is intended primarily for information-gathering. For example, you can monitor processes to determine if the number of work processes in your system is adequate, to assess if the instance is working to full capacity, to gather information for trouble-shooting, or for tuning.
In the User Overview (transaction SM04), you can display, log off, and monitor all the users active in the system who are logged on to this application server.
You can use the trace functions to follow the process of various operations in your SAP system. This allows you to monitor the system and to isolate problems that occur.
You can use the trace functions to trace SQL database accesses, ABAP programs, internal operations in the SAP system, and authorization checks using flow traces (developer traces) generated by SAP processes.
The Gateway Monitor is used for analyzing and administrating the SAP Gateway in the SAP system.
The initial screen of the gateway monitor shows all the active gateway connections on this instance.
You can monitor the RFC resources on all application servers and thus find out the load incurred by parallel RFCs on a server.
You can also dynamically change the various quotas on all servers.
You can use the log to pinpoint and correct errors occurring in your system and its environment.
If you are using your SAP system as an HTTP client or server, you can record the HTTP requests and evaluate the log file created. The Internet Communication Manager (ICM) and the SAP message server support HTTP logging.
Monday, September 15, 2008
Monitoring enables a system administrator to monitor the system. He or she can:
● Check message throughput
● Execute error and status tracking
You have called the transaction Integration Engine – Monitoring (SXMB_MONI) and the system displays the screen Integration Engine: Monitoring.
Monitoring contains a monitor for processed XML messages (transaction code SXI_MONITOR). This monitor identifies and evaluates all messages processed by the Integration Engine and produces processing statistics for them. The processed messages can be selected according to particular criteria and displayed for evaluation purposes.
Monitoring is also used to access archived XML messages (transaction code SARA with archiving object BC_XMB). These can also be selected according to particular criteria and displayed for evaluation purposes. There are two ways to search for archived messages:
● Using an archive
● Using a message ID
In both cases the system displays a list of archived messages.
Accessibility users can call the functions of transaction SXBM_MONI directly by using the relevant transaction code.
The Monitoring menu also offers the following functions:
An overview of archiving and delete jobs in the Integration Engine
An analysis of the persistence layer
Choose the required function. You cannot execute options in the menu that have the locked symbol (), because you do not have the required authorization.
The authorizations for the individual functions are tailored to requirements and are assigned as derivations of the role SAP_XI_MONITOR. They are all based on the authorization object S_XMB_AUTH.
The authorization object S_XMB_DSP controls the display of message contents. Unless the user has the authorization S_XMB_ADM (administrator), the system only displays XML messages for the current client.