Oct 16, 2014

T-Codes in Workflow

Transaction Code Description 
OOAW Evaluation paths 
PFAC Create and maintain Rules 
PFOM       Maintain assignment to SAP organizational objects 
PFOS Display assignment to SAP organizational objects 
PFSO Organizational environment of a user 
PFTC Create and maintain tasks 
PPOCW Create organizational plan 
PPOMW Maintain organizational plan 
PPOSW Display organizational plan 
SWDA Workflow Builder (Calls the Workflow Builder in alphanumeric mode) 
SWDD Workflow Builder 
SWDS Workflow Builder (Selection) 
SWDD_CONFIG Workflow configuration 
SBWP The Business Workplace 
SWDC_DEFINITION Workflow Builder administration data 
SWDC_RUNTIME Workflow runtime administration data 
SWNCONFIG Extended notifications for business workflow 
SWDM Business Workflow Explorer 
SWEINST Evaluation and maintenance of instance linkages 
SWEINSTVC Evaluation and maintenance of instance linkages 
SWE2 Evaluation and maintenance of type linkages 
SWE3 Evaluation and maintenance of instance linkages 
SWE4 Switch event trace on/off 
SWEL Display event trace 
RSWELOGD Delete event trace 
SWEC Link change documents to events 
SWED Assign change document objects to object types 
SWEQADM_1 Event queue administration 
SWEQBROWSER Administration of event queue browser 
SWETYPV Evaluation and maintenance of type linkages 
SWI1 Selection report for work items 
SWI2_FREQ Work items per task 
SWI2_DEAD Work items with monitored deadlines 
SWI2_DURA Work items by processing duration 
SWI11 Tasks in workflows 
SWI13 Task profile 
SWI5 Workload analysis 
SWL1 Settings for dynamic columns 
SWLV Maintain work item views 
SWFVISU Parameters for Work Item Visualization in the UWL 
SWO1 Business Object Builder 
SWO6 Customizing object types 
SWR_WEBSERVER Customizing Web server 
SWU_CONT_PERSISTENCE Administration of container persistence 
SWU_EWCD Wizard for event creation using change documents 
SWU_EWLIS Wizard for event creation using the Logistics Information System 
SWU_BTE Wizard for event creation using Business Transaction Events 
SWU0 Event simulation 
SWU2 RFC monitor 
SWU3 Automatic Workflow Customizing 
SWU4 Consistency check for standard tasks 
SWU5 Consistency check for customer tasks 
SWU6 Consistency check for workflow tasks 
SWU7 Consistency check for workflow templates 
SWU8 Switch workflow trace on/off 
SWU9 Display workflow trace 
SWU10 Delete workflow trace 
SWUD Diagnostic tools 
SWUE Trigger event 
SWUI Start workflows/tasks 
SWUS Testing workflows/tasks 
SWXML Display XML documents 
SWUY Wizard for linking messages to workflows 
SWWCOND_INSERT Schedule background job for work item deadline monitoring 
SWWCLEAR_INSERT Schedule background job for clearing tasks 
RSWWCOND Execute single background job for work item deadline monitoring 
RSWWCLEAR Execute work item clearing work once 
WF_HANDCUST WebFlow service handler maintenance 
WF_EXTSRV Maintain Web Service Repository 
WFWS Import WSDL files 
SWIA WI Administration Report

Difference between Data class and delivery class?

Data Class

The data class determines the physical area of the database (tablespace) in which the table is created.

You set the data class in the technical settings for the table.

There are 5 data classes only three of which are appropriate for application tables:

· APPL0- Master data (data frequently accessed but rarely updated).

· APPL1- Transaction data (data that is changed frequently).

· APPL2- Organizational data (customizing data that is entered when system is configured and then rarely changed).

The other two types are:

· USR - Customer Data class

· USR1 – Customer data class - Intended for customer’s own developments.

Delivery Class

· The delivery class controls the degree to which the SAP or the customer is responsible for table maintenance.

· Whether SAP provides the table with or without contents.

· Determines the table type.

· Determines how the table behaves when it is first installed, at upgrade, when it is transported, and when a client copy is performed.

There are the following development classes: A, S, C, L

* A: Application table (master and transaction data).
* C: Customer table, data is only maintained by the customer.
* L: Table for storing temporary data.
* G: Customer table, SAP may insert new data records but may not overwrite or delete existing ones. The customer namespace must be defined in table TRESC. To define the customer namespace use report RDDKOR54. You can start it directly from the table maintenance by choosing Customer namespace definition on the Attributes tab.
* E: System table with its own namespace for customer entries. The customer namespace must be defined in table TRESC. To define the customer namespace use report RDDKOR54. You can start it directly from the table maintenance by choosing Customer namespace definition on the Attributes tab.
* S: System table, data changes have the status of program changes.
* W: System table (e.g. table of the development environment) whose data is transported with its own transport objects (e.g. R3TR PROG, R3TR TABL, etc.)

Sep 22, 2014

HR ABAP - Infotype tables and their structures

Each infotype has a database table and a structure associated with it. As HR is related to time , we require old data as well as new data. The data we enter into the infotypes are automatically checked for accuracy and against the table entries. In simple, HR data is huge and to access data easily we require infotype. It is easy to group huge data using Infotypes.



Sep 16, 2014

Jul 28, 2014

SAP PI FAQs

SAP PI FAQs

http://wiki.scn.sap.com/wiki/display/XI/FAQ+-+Main+page

http://wiki.scn.sap.com/wiki/display/XI/SAP+XI+Questions+And+Answers

http://wiki.scn.sap.com/wiki/display/XI/SAP+XI+Interview+Questions

http://wiki.scn.sap.com/wiki/display/XI/FAQ+-+XI+SLD

http://wiki.scn.sap.com/wiki/display/XI/Michal+Krawczyk+-+FAQ+blog+-+Wiki


*SCN

Jul 25, 2014

Jun 27, 2014

SAP PI Tutorials & Blogs

Links to various helpful posts on SAP PI on SCN n other sites.

Process Integration (PI) & SOA Middleware-SCN
http://scn.sap.com/community/pi-and-soa-middleware

B2B Integration with SAP Process Orchestration
http://scn.sap.com/community/b2b-integration

Mapping Trace in SAP PI 7.31 Single Stack
http://scn.sap.com/community/pi-and-soa-middleware/blog/2013/09/18/tracing-in-sap-pi-731-single-stack

B2B Add-On and Secure Connectivity Add-On
http://scn.sap.com/community/b2b-integration/blog/2014/04/18/sp3-released-b2b-add-on-and-secure-connectivity-add-on

HowTo - Send Test Messages to the Adapter Engine (to an Integrated Configuration)
http://scn.sap.com/community/pi-and-soa-middleware/blog/2014/02/17/howto--send-test-messages-to-the-adapter-engine-to-an-integrated-configuration

B2B Add-on SP3: AS2 Log Viewer
http://scn.sap.com/community/b2b-integration/blog/2014/04/23/b2b-add-on-sp3-as2-log-viewer

Manual verification of certificate chain of trust
http://scn.sap.com/community/pi-and-soa-middleware/blog/2014/06/25/manual-verification-of-certificate-chain-of-trust

Dynamic Routing in SAP PI 7.31
http://scn.sap.com/community/pi-and-soa-middleware/blog/2014/02/25/dynamic-routing-in-sap-pi-731

Adapter Module: ReplaceString
http://scn.sap.com/community/pi-and-soa-middleware/blog/2014/04/11/adapter-module-replacestring

"AddSOAPHeaderBean" module
http://scn.sap.com/community/pi-and-soa-middleware/blog/2013/11/22/addsoapheaderbean-module

ABAP Proxy Protocols: Use Cases and Examples
http://scn.sap.com/community/pi-and-soa-middleware/blog/2012/10/19/abap-proxy-protocols-use-cases-and-examples

SAP NetWeaver PI 7.1(EHP1) and PO 7.3(EHP1) in Retrospect
http://scn.sap.com/community/pi-and-soa-middleware/blog/2012/05/21/sap-netweaver-pi-71ehp1-and-po-73ehp1-in-retrospect

Request/Response Bean for IDOC_AAE adapter
http://scn.sap.com/community/pi-and-soa-middleware/blog/2013/03/25/requestresponse-bean-for-idocaae-adapter

PI 7.3  - XML Validation
http://scn.sap.com/community/pi-and-soa-middleware/blog/2013/07/25/pi-73--xml-validation

Creating File Name from Mail Attachment using Standard Beans
http://scn.sap.com/community/pi-and-soa-middleware/blog/2013/04/02/creating-file-name-from-mail-attachment

All about XSL Languages:
http://www.w3schools.com/xsl/xsl_languages.asp

SAP NetWeaver : SAP PI (Process Integration) Overview
http://www.architectsap.com/blog/sap-netweaver/sap-pi-process-integration-an-integration-platform/

Basic things you need know about PI
http://aspireopenmic.com/2012/02/14/pi101-basic-things-you-need-know-about-pi/

Video Tutorials:-

WHAT'S NEW IN SAP NETWEAVER PROCESS INTEGRATION 7.3

SAP PI - FILE to IDOC Scenario

Jun 18, 2014

Forbidden message in ADS connection test

I face this issue and found the exact solution to fix it.

Error- ADS status Status HTTP Response 403

Solution- 

Open your Visal Admin and to go Security provider and choose the Policy Configuration "com.sap/com.sap.engine.services.webservices.tool~wsnavigator". 
Select the tab "Security Roles". The applied security roles for WSNavigatorRole is most likly "administartors". Please change this to "all" if you want that everyone can at least call the wsnavigator application or restrict it by other criterias, BUT make sure your adsuser can access it! Change your changes

Now test the ADS RFC Connection from SM59. It should work now.


Jun 2, 2014

Commonly Used Transactions for EDI Support

Transaction               Function
 IDOC Maintenance
 WEDI                      SAP Easy Access - EDI and IDOC Basis
 WE02/05/09             Change/Display/Search IDOC
 WE07                      IDOC Statistics (IDOCs in Error)
 WE19                      Inbound IDOC Testing Tool
 BD87                       Process IDOC
 Business Documents  
 VA03/02                 Display/Change Sales Order
 VL03/02N               Display Outbound Delivery
 VF03/02                  Display/Change Invoice  
 Master Records
XD03                      Display Customer Master Records
MM03                     Display Material Master Records
XK03                      Display Vendor Master Records
VD53                      Customer Material Information Records (CMIR)
 Electronic Business Support
 WE20                      Electronic Trading Partner Profiles
 WE21                      Define SAP IDOC Ports
 VV12/22/32             Edit Sales/Shipping/Billing Output Condition
 SAP Data
 WE60/62                  SAP Data Dictionary
 SM30                       SAP Table Maintenance 
 CUNI                       ISO Units of Measure
 SE16                        View Table
 ABAP and Scheduled Jobs
 SM37                       SAP Job Log
 SE37                        Display Function Module
 SA38                        ABAP Program Execution
 EDI development
WE31                       Idoc segments
WE30                       Idoc types
WE81                       Message types
WE82                       Idoc type/message
WE31                       Outbound process code
BD51                        ALE attributes
WE57                       Message/application object
WE42                       Inbound process code

May 5, 2014

HTTP Port number of SAP System

How to find the HTTP Port number of SAP System?


Go to the Transaction SMICM
Choose from the menu "GOTO -> Services".
 In the screen to follow, you can find the HTTP Port number of that system.

Mar 27, 2014

Understanding infotype Time constraint

  •  Infotypes are information units in the Human Resources Management system. Groups of related data fields are bundled into infotypes.
  • Infotypes structure information, facilitate data entry and allow data to be saved for specific periods. Infotypes serve as templates for users to enter data. From a database point of view, infotypes provide a data structure and a set of coherent data records. 
  •  The infotypes Actions 0000,  Organizational Assignment 0001, Personal Data 0002, and Payroll Status 0003 are prerequisites for entering a personnel or applicant number.
  •  Save the infotypes at intervals to build up an infotype history. The system stores a validity period for each infotype record. Therefore, several data records usually exist for each infotype of an employee, and each record has a different validity period.
  •  You use a time constraint to determine how the data records of an infotype react to each other in terms of time.
  • Several infotypes have subtypes, which break down information further. For example, technically speaking, the address types for infotype Address 0006 represent the subtypes
  • Each infotype and subtype has a time constraint.
  •  Time constraint 1: Complete saving with no overlaps at any time, that is, one valid data record of the relevant infotype must exist during the duration of the employee's employment at the company.
  •  Time constraint 2: Incomplete saving without overlaps at any time, that is, of an infotype may exist at a given time. No more than one valid data record of the infotype can exist at any given time.
  • Time constraint 3: Incompleteness and overlaps permitted, that is, any number of valid data records of an infotype may exist at any given time.

Time Constraints A: Only one record may ever exist for this infotype. It is valid from 01/01/1800 to 12/31/9999. Splitting is not permissible. View V_T582B Infotypes which are Created Automatically controls whether the system automatically creates the infotype record for an employee hiring or an applicant data entry action. Infotypes with time constraint A may not be deleted.
Time Constraints B: Only one record may ever exist for this infotype. It is valid from 01/01/1800 to 12/31/9999. Splitting is not permissible. Infotypes with time constraint B may be deleted.
Time Constraints T: The time constraint varies depending on the subtype.
For the Addresses infotype (0006), you can assign a different time constraint for each subtype. In this way, you can make sure that a main address always exists for the employee and you can also enter temporary residences, if necessary.
Time Constraints Z: Refers to time management infotypes. The time constraint for these infotypes depends on the time constraint class defined in view V_T554S_I Absence: General Control. Collision checks are defined in view V_T554Y  Time Constraint Reaction.

Mar 12, 2014

ABAP Tips n Tricks!

Some recommended Points everybody should remember when developing (ABAP)

http://scn.sap.com/community/abap/blog/2014/02/18/some-recommended-points-everybody-should-remember-when-developing-abap


*SCN

Feb 19, 2014

Developer Key

Developer Key and its requirement (DEVACCESS table)
 o    What is Developer Key?
The developer key is a combination of your installation number, license key (that we get from marketplace http://service.sap.com/licensekey  and the user name. We need this for each person that will make changes (Dictionary or programs) in the system. 
 
 
o    Why Developer Key is required?
SAP developers require two things before they can actually do development work in SAP - right authorizations and a developer access key. As with everything else in SAP, when a developer tries to execute a transaction, he will need the required authorizations in her profiles. In addition, he needs to be assigned a developer access key. The authorizations can be checked in the user master records while the developer access key can be checked using table DEVACCESS. Table DEVACCESS will show the user ID and the developer key assigned to the user ID. You should only expect to see name of developers in this table.
o    What happens when the entry for a developer is deleted in the DEVACCESS table but the developer continues to use the same user ID?
The developer can still use the old developer access key. 
The reason: Developer access key is nothing but an algorithm based on system number and SID and some other system values (SAP does not reveal the information). The developer access key is validated by SAP using a Kernel level C system program ''CHECK_DEVELOPER_KEY'. So, even if the developer access key has been deleted for a user ID in the DEVACCESS table, he can still use the same developer access key.
 
 
 
o    Which Table is the Developer Key Stored In?
If we would like to look up at your developer key and save it and have it available for the next system refresh. 
The table name is DEVACCESS and can be viewed with SE16 and SE11.
 
For new ABAP developer, we will be prompt for the developer if we are trying to create a program using the standard SAP naming convention.
 
Customer own created program should all start with a "Y" or "Z".
 
 
 
o    How to register developer in marketplace?
Login into sap marketplace and go to below mentioned tabs as shown in screen. 
 
 

 Click on “Register Developer” 
 
 

 
 Insert the SAP User ID and select relevant installation number. 
 
  
  
Then click “register” button.
 
Then developer key will generate and appear at the bottom of the screen. 
 
  



Jan 19, 2014

ABAP FAQ

ABAP FAQ..

http://sap-interview-questions-and-answers.blogspot.de/2012/07/abap-interview-questions.html

How to change Transport request from Released to Modifiable

Step 1: Go to SE38 – Execute Program RDDIT076.  Step 2: Give your released requests number and execute again. Step 3: After executing, yo...