PI 7.1 including Enhancement Pack1

Hello,
I'm trying to find information, to see if it's possible to upgrade the existing PI 7.0 (on Windows 32bit) to PI 7.1 inc EhP1. All I see is 64bit info everywhere? is it really, I can't move forward with this upgrade or I'm not looking correctly?
Spent a lot of time..so far nothing..any idea if it's supported for 32bit?
Thank you for reading.
Mark.

Hi,
Check for installation queries by downloading the guide from service marketplace, below is the link;
[Service Marketplace Link|https://websmp208.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000702775&_OBJECT=011000358700000921782007E]
Regards,
Gautam Purohit

Similar Messages

Installaing decentral Adapter Engine (Java EE) 7.1 Including Enhanc

Dear All
we are installaing decentral Adapter Engine (Java EE) 7.1 Including Enhancement package 1 on Linux with database DB2.To do installation we have followed the installation guide "Adapter Engine (Java EE) 7.1 Including Enhancement Package 1 on Linux: IBM DB2 for Linux, UNIX, and WindowsTarget"
Accoridng to that document "In the Welcome screen, choose the required SAPinst installation option under the node SAP EHP1 for SAP NetWeaver Process Integration 7.1Installation >OptionsOptional Standalone Units >Partner Connectivity Kit." we have followed the same.
The installation has been completed successfully.But to do post-installation activities the java url in not comming up.
,we have tried with physical host and ip address as well.From os level we have found that server0 process is in running status.
I am not sure why the installation guide is asking us to follow Process Integration 7.1Installation >OptionsOptional Standalone Units >Partner Connectivity Kit?
Will you please let me know whether this is the correct procedure for Installation of Adapter engine on Pi 7.1 EHP1
is there any prerequisite steps are there for adapter enginee
Thanks and Regards
ravikiran.CH

Hello
From your description, it appears that you have installed a PCK and not a decentral Adapter Engine.
I guess you need to follow Process Integration 7.1Installation
-> Optional Standalone Units
-> Adapter Engine
You can undeploy the PCK by following the steps in the note #1295094 Initialization of PI 7.1 XITOOLS fails.
Regards
Mark

NW7.0 Enhancement Pack1 and BI7.0

Gurus:
I am installing a BI7.0. However, the sapinst on the DVD reads:
"As of SAP NW7.0 with enhancement pack 1, you can install dual stack ONLy with usage type PI and MI."
But I want a dual stack BI7.0.
What should I choose? PI or MI?
Thanks!

So you mean enhancement pack1 is NOT for BI?
We are going to install dual stack SRM. No enhancement pack for it as well?
Any OSS note about that?
Thanks!

Copying Standard Reports including enhancements

Dear All,
Im tried to copy standard report mb5b but enhancements in that is not getting copied.
Please guide me.

Hi Dilip,
Which enhancements are you talking about ?
I dont see any enhancement in program RM07MLBD.
Best regards,
Prashant

An error occurred while processing option SAP NetWeaver 7.0 including Enhancement Package 3

I have error when I try to install SAP NetWeaver Application Server ABAP 7.03 64-bit Trial.
can someone help me???

Hello Sávio,
probably you have a virtual CD drive mounted on the G:\ volume, uninstall the virtual drive software and restart the SAP installation from scratch.
Regards,
Valerio

How to include an enhancement package with upgrade without Solution Manager

Hello,
I have been trying to do an upgrade from SAP R3 46C to ERP6 in my sandbox. I want to include Enhancment package 3 with the upgrade. I have tried using the Solution Manager to download the Enhancement package and it work fine except that it did not create the XML Stack configuration file that the upgrade is looking for. Therefore I downloaded the DVD for Enhancement package 3 and included that in the mounted CDs in the PREPARE portion of the upgrade and it does not recognize it.
Now for my question, is there a way to include the Enhancement package with the upgrade without using Solution Manager? If so, could someone please let me know where to find the information or share the procedure with me?
Thank you in advance,
Ron

The EPs are just like support packages (optional); if the upgrade is not letting you put it during upgrade then just do it once the upgrade is completed.

Enhance all photos in an event

How do i enhance all photos in an event instead of enhancing one by one?

There's a 3rd party application that can do bach edits including enhancement of photos in iPhoto: iPhoto Batch Ehancer.
OT

Call enhancement class method from Bus. workflow task

Hi all,
I recently enhanced a global class from SAP (add a new method). Now I would like to call it from a workflow task (ABAP Class object used in the task). So it seems that only "native" methods from the class itself can be selected for the object method of the task.
Same issue if I try to call it via secondary methods options...
Last idea I have before the repair is: retrieve the instance saved into the WF container via a custom class interfacing IF_IFS_SWF_CONTAINER_EXIT (program exit) and call the enhanced method from the method proposed in this interface.
Maybe someone had the same issue? Anyone could help or propose solution?
Many thanks in advance for your help,
KR,
Olivier

I think it might qualify for an OSS message.
There was simmilar note for BADIs which was corrected: https://service.sap.com/sap/support/notes/1156392
CL_SWF_UTL_DEF_SERVICES which is used in PFTC to determine callable methods doesn't include enhancements when calling function SEO_CLASS_TYPEINFO_GET (parameter WITH_ENHANCEMENTS is default FALSE)

Enhancement Package 5 for SAP ERP 6.0 - Webinar Series - Oct-Nov 2011

Webinar Series: Enhancement Packages for SAP ERP
Innovation Made easy!
SAP enhancement packages (EHPs) are optional add-on packages that enable you to selectively install and use new functions without a major release upgrade. Since May 2011 enhancement package 5 for SAP ERP 6.0 is general available. With this latest enhancement package more than 500 business functions are delivered in order to improve or enhance the various SAP ERP application areas, industry solutions and usability.
Customers running SAP ERP 6.0 can benefit by installing SAP enhancement package 5 and switch on any of the new business functions.
Get insights and an overview of whatu2019s new with SAP enhancement packages and how innovation is made easy. Join the upcoming webinar session series covering what you need to know about EHPs and activating new functions and the major improvements in SAP ERP Financials, SAP ERP HCM, SAP ERP Operations and the areas of usability and user interfaces.
In one-hour sessions SAP Experts will introduce the new functions; provide a u201Cliveu201D experience on selected topics and will be available to answer your questions.
Target group: These webinars are pointed to IT-managers, business managers, business analysts and business process experts.
Cost: Joining these webinar series is free of charge.
Language: English
Dates: Oct 13 to Nov 29, 2011
Region: Americas
Topics included
     Enhancement Packages for SAP ERP: Innovation Made Easy - Learn how to do it
     Enhancement Packages for SAP ERP: What is new in SAP ERP Operations?
     Enhancement Packages for SAP ERP: What is new in SAP ERP HCM?
     Enhancement Packages for SAP ERP: What is new in SAP ERP Financials?
     Enhancement Packages for SAP ERP: What is new for User Interface and Usability?
To register please visit http://www.sap.com/mk/get/ehp

Hi Partson,
It is needed to connect this system with solution manager and create stack.xml using
maintanance optimizer. The main aim of this is to let you know what usage types/ functionalities are to be
selected from stack.xml.
It is also needed to download all the required support packs/ addons using maintanance optimizer.
If you have DVDs containing the same product that matches with stack.xml, you can provide them.
But the safest way is is to give all the tasks to solution manager , It will create , and download neccesary sps, addons to your
download basket.
Thanks and Regards
Purna

Enhancement SPOT ES_SAPLITO2

Hi ,
Can anyone suggest how to activate the enhancement spot ES_SAPLITO2.
Actually I have modified the code inside the Enhancement Implementation DIMP_GENERAL_SAPLITO2 which include enhancement section \PR:SAPLITO2\EX:ITOB_CHECK_SERIALNO_04\
Need to modify the code inside this section which I have done.
Also activated the code and implementation.
Now I am not able to see this new code in the transaction EG44 which is for Device Creation.
Switch is - DIMP_GENERAL which is off.
Could you please suggest the procedure so that we will be able to execute this code in EG44 transaction.
This enhancement spot is for EG44 transaction only.
thanks in advance.
-cheers
Baajeerao Dabhade
+44-7964560976

There are number of user exits for this purpose., check function group XM02.
If you are really intent on using ES, navigate to the package MEREQ, where I believe you will be able to edit the enhancement spots.
Rgds
Bhavani

New to ABAP Enhancements

Hi Experts,
As I am new to ABAP Enhancements can anyone guide with the navigations on how to proceed for creating an enhanced object.I will be helpful if u can provide it with some examples.
Thanks & Regards,
Naresh

Hi,
Overview of Customer Exits
The SAP application programmer plans possible application enhancements
in an application and defines the necessary components. These
components are combined in SAP enhancements.The programmers document their enhancements as best they can so that customers can implement the enhancements without having to analyze the program source code or the screen source code.
First, create an enhancement project and then choose the SAP
enhancements you want to use.
Next, edit your individual components using the project management
function and document the entire enhancement project.
Finally, activate the enhancement project. This activates all the component
parts of the project.
The transaction, CMOD, starts the project management function. You
must give your enhancement project a name. SAP recommends that you
think up a naming convention for all your projects. You caninclude the
transaction or module pool of the project in its name. All the enhancement
project names must be unique.
Next, go to the attributes of the project and enter a short text describing
the enhancenent project. The system inserts all the other attributes of the
project, such as created by, created on, and or status.
Use the project management function to assign SAP enhancements to
customer enhancement projects. Enter the names of the SAP enhancements
you want to use on the appropriate screen.
The search function gives you a catalog-like overview of existing SAP
enhancements. From there, you can select the enhancements that are of
interest to you.
Use the product management function to edit the components of your
enhancement project.
Depending on whether the component you are editing is a function
module, a menu entry, or a subscreen, you branch to either the Function
Builder, a dialog box for entering menu entries, or to the Screen Painter.
Activation of an enhancement project affects all its components. After it
has been activated successfully, the project has the status, active.
During activation, all programs, screens, and menus that contain the
components that belong to the project are regenerated (programs at the
time they are executed). After activation, you can see the effect of the
enhancements in your application functions.
The Deactivate function allows you to reset the status of an active
enhancement project to inactive.
When the enhancement project was created, you should have assigned
it to a change request. Each of the component pieces, such as include
programs, subscreens, and menu exits, should be assigned to the same
change request. Using the same change request allows you to transport
the entire enhancement at the same time.
Function Module Exits
Function module exits allow customers to implement additional logic
in application functions. SAP application programmers define where
function module exits are inserted and what type of data they transfer.
SAP programmers also create the corresponding function modules of an
exit complete with short text, interface, and documentation, as well as
describing the intended purpose of each function module in the SAP
documentation.
You write the source code for the function modules yourself. If need be,
you can also create your own screens, text elements, and includes for the
function group.
The system processes your ABAP code when the enhancement project of
which your function module is a component is activated. Function module
exits have no effect prior to enhancement project activation.
The exit function module is called in the PAI logic of a screen at a position
determined by the SAP application developer. Within the function module,
the user can add the functions in the customer namespace using an include.
To call function modules, use the ABAP statement: CALL
CUSTOMER-FUNCTION nnn, where nnn is a three-digit number. The
programmer must also create the function module the developer wants to
call and its related function group.
These function modules always belong to function groups, the names of
which begin with X (X function group).
The following naming convention applies to function modules:
 Prefix:EXIT
 Name: Name of the program that calls the function module
 Suffix: Three-digit number
The three parts of the name are separated by an underscore.
The CALL CUSTOMER-FUNCTION statement is only executed after
the enhancement project has been activated. Multiple calls of the same
function module are all activated at the same time.
The most frequently asked question concerning enhancements is how can
you see if an application program offers a function module exit? There are
a number of ways to find the answer to this question.
To see quickly if an application program offers a function module exit, you
can follow the path on the left side of the figure: The menu path System→
Status always displays the name of the current application program. In
this example, a suitable character string would be CALL CUSTOMER.
Click the Find icon and search globally in the program. If your search doesnot provide any results, you can define a larger search area. Determine
the environment for the corresponding program and look for the specific
character string in the program environment.
The right side of the figure shows you howto find the name of the required
enhancement using search tools. You can restrict the search in the SAP R/3
Repository Information System using different criteria. These are:
 Development class (also try generic entries)
 Technical name of the enhancement
Use the project management, transaction: CMOD function, to edit the
function modules for function module exits.
Use the button for editing components to go directly to the function
module editor (display mode).
Do not change the function module itself. It is especially important that
you do not alter the interface in any way. The function module, contains
an INCLUDE statement for an include program that you have to create
in the customer namespace.
Select the include name beginning with ZX. This automatically takes you
to the editor of the include program, where you can enter your code.
To understand how an X function group works, you need to understand
how a normal function group works:
 A function group consists of includes. The system assigns unique the
names to the includes for different objects. Some of the include names
are simply proposals and some cannot be changed.
 Global data is stored in the TOP include. This include is generated
automatically when a function group is created.
 Function modules are stored in includes with sequential numbering
and they, in turn, are all stored in an include ending with UXX.
 Although can freely choose the names of the includes for all other
objects such as subroutines, modules, and events, it is a good idea
to accept the proposed names.
Exit function groups created by SAP application programmers for
enhancement exits contain include programs that begin with either LX or
ZX. You can only edit includes beginning with a Z because they are stored
in the customer namespace.
No further function modules may be added to the function group.
The include program, ZxaaaUnn contains the source code for the function
modules of a function module exit.
SAP application programmers can declare global data in include program,
LXaaaTAP.
You can declare your global data in the include, ZXaaaTOP.
Include program, LXaaaTOP also contains the FUNCTION-POOL statement,
which may not be changed. For this reason, you must always include the
message class in parentheses when outputting messages. For example,
MESSAGE E500 (EU) .
The INCLUDE statement for program ZXaaaUnn is in a FUNCTION -
ENDFUNCTION block. Because of this, neither events, nor subroutines(
FORM ), nor modules ( MODULE ) are allowed here. They can be created in
separate includes, which is explained later. Data declarations made here
with DATA are valid locally in this function module.
The SAP application programmer can also make a proposal for the source
text. In this case, an INCLUDE LXaaFnn is created, where nn is the
internal number for the function module in the include, LXaaaUXX ).
Documentation is also provided within the SAP enhancement. You can
copy the source code fromthis include into your own customer include
program, ZxaaaUnn, using the project management transaction.
You can create your own text elements for the function group.
SAP application programmers can supply you with default subroutines
in the include, LXaaaF01.
There could be further includes containing specific subobjects:
 LX...F01 contains the subroutines delivered by SAP
 LX...E01 contains the events belonging to the X function group
 LX...O01 contains the PBO modules for the screens to be delivered
 LX...I01 contains the corresponding PAI modules
Subroutines, modules, and interactive events (AT) are created as include
programs and included enhancements using the include program,
ZXaaaZZZ.
Additional includes must adhere to the following naming convention:
 ZXaaaFnn for subroutines
 ZXaaaOnnforPBOmodules
 ZXaaaInn for PAI modules
 ZXaaaEnn for events
You can use CALL SCREEN to call your own screens. Create the related
include programs for the Process Before Output (PBO) and Process After
Input (PAI) modules in the include program, ZXaaaZZZ .
Use forward navigation (select an object and then double-click it) to create
your own screens and modules.
Screens created in this way are automatically given the name of the
function modules main program, SAPLXaaa . The PBO modules for these
screens can be found in the include, ZXaaaO01 , and the PAImodules
in the include, ZXaaaI01 .
You can enhance SAP applications by adding your own processing logic
at predefined points.
Such enhancements can include your own screenswith their corresponding
processing logic and graphical user interface as well as text elements
created by customers.
Regards,
Balaji Reddy G
***Rewards if answers are helpful

MDSD : Problems in exporting Enhancement Project

Hi Experts,
I am having some problems in exporting the Enhancement MDSD project.... Please see the detailed description below....
Firstly I created a Standard MDSD project from MDSDSRC.zip file, then I created an Enhancement project from MDSD.jar file.. while creating this enhancement project I have included Standard project in it under Java Settings -> Projects & add project..
exporting the project in ..
1st way-
Project Right click -> Export -> Include Enhancement & Standard project under
"select the resources to export" -> choose checkbox - "Export generated class fiels & resources" & "Export java source files & resources" -> Next -> Next -> Select "com.sap.dsd.appctrl.DSDMain" in select the class of the application entry point -> Finish.....
It gives me errors as mentioned below..
1. Problem writing /MDSD_S1/java/ProjectConfig.properties to JAR: duplicate entry :     ProjectConfig.properties
2. Problem writing /MDSD_S1/.classpath to JAR: duplicate entry :    .classpath
3. Problem writing /MDSD_S1/.project to JAR: duplicate entry :    .project
2nd way-
Project Right click -> Export -> Include Enhancement & Standard project under
"select the resources to export" -> choose checkbox - "Export all output folders for checked projects" & "Export java source files & resources" -> Next -> Next -> Select "com.sap.dsd.appctrl.DSDMain" in select the class of the application entry point -> Finish.....
It gets exported properly but then when I replace that MDSD.jar file in
"C:\Program Files\SAP Mobile Infrastructure (C)\lib" folder with the standard MDSD.jar file which comes from SAP & run the MDSD application from mobile client it gives me an error as mentioned below..
java.lang.NoClassDefFoundError: com/sap/mbs/tools/signature/SignCanvas
Here i got some weird thing....
The standard MDSD.jar file based on which the MDSD application works has com->sap->mbs,uxe,tc,sxe,spe,mbs,dsd packages present whereas the enhancement project which I created from this same standard jar file & exported it has only dsd package. So this exported jar file doesnt include above mentioed SignCanvas class and hence its giving me an error.
Pls guide me further in this issue....
Thanks in advance....
Rajesh
Edited by: RAJESH SHINDE on Apr 8, 2009 11:21 AM

Hi Rajesh,
I think you are trying to enhance the MDSD 3.0 application. And the SignCanvas which you are mentioning is present in the mbs folder of the of the standard application jar. As you have told below if the jar you have created doesnot have these packages, the mentioned issue is happening.
Regards,
Vishwanath
Edited by: Vish on Apr 22, 2009 9:09 AM

Idocs - Enhancements!

Hi Friends!
 Can any one pls tell what all the enhancements which u ve worked on IDOCS.
 Pls give step by step detail in Creation of segments & FM coding Please.
 Looking for your Help.
 Thanks In Advance.
 Rahul.

Hi Rahul..
These are the Steps for IDOC enhancement.
IDOC EXTENSIONS
SAP delivers Basic IDOC types such as DEBMAS02, MATMAS02.
By extending the Basic IDOC type, you are actually creating a new IDOC type.
You create a new segment with the additional fields. This new segment has to be associated with one of the existing Basic IDOC segments. Then you create a new extension type, which is associated with the Basic IDOC type. This results in a new IDOC type. In order for ALE function modules to relate to this new IDOC type, the IDOC type is linked to the corresponding message type.
Note: that you should not add fields to existing segments but should create a new segment and associate it with an existing segment.
In our example, the Basic IDOC type DEBMAS02 is used to communicate Customer Master data to the SAP Customer Master application. Even though the application has a screen to enter and store a contact personâs business address DEBMAS02 does not have a segment or fields that communicate the contact persons business address. If your business requires that this business address be communicated to the other system through the ALE interface for Customer Master, then you have to extend the DEBMAS02 IDOC type, and enhance the corresponding ALE function module.
In DEBMAS02 the contact person fields are present in segment E1KNVKM and the business address of the contact person is stored on the SADR SAP table. You need to create a new segment, Z1SADRX, that is associated with E1KNVKM. This will be done in the process of creating an extension type ZDEBMASX. This extension type will then be associated with a new IDOC type, ZDEBMASZ. IDOC type ZDEBMASZ will be linked to message type DEBMAS for Customer Master. The final step in the IDOC extension process is to check the new objects. This check also verifies the structural integrity of the IDOC type. Letâs look at each of these steps in more detail.
1. Create an Extension Type and a New Segment.
Determine the fields on table SADR that you are going to provide for in the new segment Z1SADRX. You need fields for name, street, city, region, and country to give the business address of the contact person. You also need fields for the address number. ADRNR is a field in SAP tables such as SADR that uniquely identifies the address of an entity. This field is cross-referenced from other tables to the SADR table to obtain the full description of the address. Because this is an IDOC type for master data, the first field of the new segment will be MSGFN. The message function field informs the receiving system of the action to be taken for that particular segment. In the code that you write for populating the new segment, the value of the message function is the same as that of the parent segment E1KNVKM. In all, you will have 12 fields in segment Z1SADRX (see Table 1).
To create an extension type and new segment:
Use transaction WE30 or from WEDI go to Development -> IDOC types.
Enter ZDEBMASX for Object Name.
Choose Extension Type.
Click on Create.
You will see a pop-up screen. Choose Create New, and enter a description. For version 4.x, enter DEBMAS02 in the Linked Basic Type field. Enter.
You will see a screen with ZDEBMASX and its description in the first line. Click on this line, and press Create. For version 4.x, expand the tree of segments, and place the cursor on E1KNVKM.
You will see a pop-up screen. Enter E1KNVKM as the reference segment. Enter.
For 4.x, press Create after placing the cursor on segment E1KNVKM.
You will see a line appear with E1KNVKM hierarchically below ZDEBMASX, with a description "Customer Master contact person (KNVK)."
Click on this line and press Create. You will receive a message indicating that the new segment being created will be a child segment of E1KNVKM. Enter. A pop-up box appears for the new segment.
Enter Z1SADRX as the segment type, 1 for Minimum, 1 for Maximum. Leave Mandatory segment unchecked. These entries imply that there is only one Z1SADRX segment for every occurrence of the E1KNVKM segment, and also that this segment is not mandatory. Note that if the parent segment is not mandatory, then the child segment should not be mandatory, because this could result in a syntax error during the creation or processing of the IDOC.
For 4.x, you must first create the IDOC segment Z1SADRX (Iâll explain why in a moment) from the menu path WEDI -> IDOC -> Development -> IDOC Segment.
Click on Segment Editor.
On the next screen, click on Create.
Enter a development class for the object. Enter.
This will take you to the screen for segment definition. Enter a description for the segment. Enter the field name, data element, and the data element documentation name. In most cases, all three fields may have the same values. If you are using a field in the segment that is not present in the ABAP/4 data dictionary, you must first create the domain, data element, field, and appropriate documentation before using it in the new segment.
Enter these three columns for all 12 fields. Save.
Click on Generate/Activate, F3 to step back.
From screen Maintain Segment, go to Segment Type -> Release. A checkbox now appears beside the segment definition Z1SADRX (see Figure 2). Check this box. Save.
Save again to store the descriptions of the segment, F3 to step back.
Save the extension type.
It is possible to have several new segments with relevant Basic IDOC type parent segments in a single extension type. However, you can form only one IDOC type based on a single extension type.
2. Create an IDOC Type.
The next step is to create an IDOC type by associating the extension type that you created with the Basic IDOC type. This is a simple process:
From transaction WE30 or WEDI go to Development -> IDOC Types.
Enter ZDEBMASZ for Object Name.
Click on IDOC Type.
Click on Create.
Enter DEBMAS02 for Basic IDOC type.
Enter ZDEBMASX for extension type.
Enter a description.
Enter.
You will see a display of the composite IDOC type with all segments, including Z1SADRX (see Figure 3).
It is possible to associate only one extension type with a Basic IDOC type for a given IDOC type. However, you can have multiple new segments in an extension type.
3. Link IDOC Type to Message Type.
The next step is to link the new IDOC type to its corresponding message type. This is important, because this relationship is referenced in the partner profile parameters where you specify the message type and IDOC type to be used for that particular representative system. To link the message type:
Use transaction WE82, or from WE30, go to Environment -> IDOC Type / Message Type, or from WEDI go to Development -> IDOC Type -> Environment Î IDOC Type / Message Type.
Click on Display <-> Change.
Click on New Entries.
Enter DEBMAS for message type.
Enter DEBMAS02 for Basic IDOC type.
Enter ZDEBMASX for extension type.
Enter your SAP R/3 release number for Release.
Save.
This data is stored on the EDIMSG table and is accessed by several ALE processes to relate the message type to the IDOC type.
4. Check the IDOC Type.
Before checking the IDOC type for consistency, it is important to perform another step that releases the extension type to the IDOC type:
From WEDI go to Development -> IDOC Types -> Extras -> Release Type, or from transaction WE30 go to Extras -> Release Type.
For the Object Name ZDEBMASX and radio button Extension Type, click Yes.
The extension type has now been "released."
You canât edit the extension type once itâs released. To cancel the release for further editing or deactivation, go to WE30 Î Extras Î Cancel release. The final step in the IDOC extension process is checking the validity of the IDOC type:
From transaction WE30 or WEDI go to Development -> IDOC types.
Enter ZDEBMASX for Object name.
Click on Extension Type.
From the Development Object menu select Check.
Repeat the operation for IDOC type ZDEBMASZ.
ALE FUNCTION MODULE ENHANCEMENTS
Having extended the IDOC type to contain additional fields for an inbound or outbound application, you now want to enhance ALE function modules for populating the additional segment on the outbound or applying the additional segment data on the inbound application.
For master data distribution, from SALE go to Extensions -> Master data distribution -> Setup additional data for message types. Search for message type DEBMAS in this example. You see an entry for DEBMAS associated with function module MASTERIDOC_CREATE_SMD_DEBMAS. This data is stored on table TBDME. The function module names for all master data message types follow this pattern: MASTERIDOC_CREATE_SMD_messagetype. This function module calls another function module of name MASTERIDOC_CREATE_DEBMAS or MASTERIDOC_CREATE_messagetype. Search for the words customer function, and you find several hits that can be used to add code to the function module.
From WEDI got to Control -> Inbound process codes -> Inbound with ALE service -> Processing by function module (transaction WE42), or from WEDI go to Control -> Outbound process codes -> Outbound with ALE service -> With function module (transaction WE41). There will be function modules associated with the process codes. For inbound, the function modules usually follow this pattern: IDOC_INPUT_messagetype: for example, IDOC_INPUT_CHRMAS for inbound characteristics master.
Use transaction WE57 or from WEDI go to Development -> Message/Application Object. The entries list the function module, Business Object, message type, and IDOC type that are used for inbound ALE/EDI interfaces.
Customer functions are not specific only to ALE and EDI but also to all programs/modules in SAP R/3. Customer function is a SAP enhancement component; the other two types are menu and screen enhancements.
All customer function exits are maintained in SAP enhancements and are found by using transaction SMOD. After executing transaction SMOD, pull down (F4) on the enhancement name field, and execute again. This provides you with a list of all SAP enhancements available. SAP enhancements are grouped by development class pertaining to an application area. Choose Application development R/3 SD master data distribution for development class VSV to lead to a screen that lists VSV00001 as an enhancement (see Figure 5). Press Component +/- to display its function exit components. There are four possible components listed, all of which are function exits (and are function modules) that are called from the ALE function modules in the form Call Customer Function Î001â. This is a special occurrence of the ABAP statement Call. Go to item Exit_SAPLVV01_ 001, which you need to enhance for the Customer Master outbound example of an IDOC extension. In the ALE-function module MASTERIDOC_CREATE_DEBMAS, the statement CALL Customer Function 001 is translated in the background to call component EXIT_SAPLVV01_001. Although this function exit can be edited using transaction SE37, you will use a simpler approach.
When you use SAP enhancements and their components, you manage them with an SAP object known as a project, which is like an envelope containing the selected enhancements and their components. A project can be used to control the execution of components and to transport them to other clients and instances in SAP. Basically, the process involves creating a project, including enhancements and components that are to be enhanced, editing the components, and then activating the project. The following process creates a project for our example Customer Master IDOC extension:
Execute transaction CMOD.
Enter name of project, say CSTMAST1.
Click on Create.
Enter a description of the project.
Save.
Click on SAP Enhancements.
Enter VSV00001 for Enhancement.
Save.
Once youâve created the project, edit the function exit components and activate the project. Remember that the code in the function exit enhancement will execute only if the project is activated.
Outbound interfaces. In an outbound ALE interface you use function exits (customer functions) to populate additional segments created by an IDOC extension or to modify the existing IDOC data segments as per business requirements. Previously, you identified that enhancement VSV00001 has a component EXIT_SAPLVV01_001 (function exit), which can be used for populating the additional data segment Z1SADRX that you created in the IDOC extension ZDEBMASX (IDOC type ZDEBMASZ, based on Basic IDOC type DEBMAS02). You also learned that the ALE function module that calls this function exit is MASTERIDOC_CREATE_DEBMAS, which has a statement Call Customer Function 001.
Browse the function module MASTERIDOC_CREATE_DEBMAS using transaction SE37. You will find that this customer function is invoked for every segment of IDOC type DEBMAS02. In fact, the function exit is called soon after the creation of an existing segment has been populated with data and appended to the IDOC data table (internal table). Also, the function exit is exporting the message type, IDOC type, and the segment name and is importing the IDOC extension type. It is also passing the IDOC data internal table. This indicates that the ALE function module is allowing you to populate additional segments for every existing segment and modify the existing segmentâs data.
Letâs write ABAP/4 code to accomplish the task of populating IDOC segment Z1SADRX with a contact personâs business address:
From SE37, display function module MASTERIDOC_CREATE_ DEBMAS.
Find Customer Function 001.
Double-click on 001.
The function EXIT_SAPLVV01_001 will be displayed.
Double-click on INCLUDE ZXVSVU01.
You will be asked to create a new include object. Proceed as desired.
Enter code (as in Listing 1).
Be sure to perform a main program check (Function Module -> Check -> main program) and extended program check (Function module -> Check -> Extended check).
Now that you have extended the IDOC and enhanced the ALE function module based on the requirements for the contact personâs business address on the Customer Master, letâs test the interface. You should create a logical system and define a port for this interface. You should also configure the Customer Distribution Model to indicate that message type DEBMAS is being distributed to this logical system. The only difference in configuration between a regular outbound ALE interface and an enhanced one is the partner profile definition. While maintaining the outbound parameters of the partner profile, make sure the IDOC type is ZDEBMASZ. The fields for Basic IDOC type and extension type are automatically populated with DEBMAS02 and ZDEBMASX, respectively.
To maintain the contact personâs business address of a customer:
Use transaction BD12 or from BALE go to Master Data ->Customer -> Send and send that Customer Master record by executing the transaction after filling in the relevant fields such as customer number, message type, and logical system.
Use transaction WE02 or WE05 to verify the IDOC created. You should see the new segment Z1SADRX populated with the correct data.
With SAP releases below 4.5B, you cannot capture changes to business address through change pointers because a change document object is not available for capturing business address changes, and also earlier releases have not been configured to write change documents for a contact personâs business address. If you would like this functionality, you can either create change document objects, generate function modules to create change documents, and perform ALE configuration to tie it in, or make a cosmetic change to the contact person screen data while changing the contact personâs business address so that it gets captured as a change to the Customer Master. Subsequently, the ALE enhancement that you performed captures the contact personâs business address.
Inbound interfaces. The process for enhancing inbound ALE interfaces is similar for outbound, with a few exceptions; specifically in the coding of customer functions (function exits) for the ALE/EDI function modules.
The first step is to create an IDOC extension for the specific Basic IDOC type by adding new segments at the appropriate hierarchy level: that is, associated to the relevant existing segment. Populate the data fields on the new segments with application data by the translator or external system/program before importing them into the R/3 System. Then, find the ALE function module that is invoked by the inbound processing. By browsing through the code or reading the documentation on the function exit enhancements using the SMOD transaction, identify the function exit in which you should place your code. The technique used in the code to post the additional or modified IDOC data to the application can vary based on the application rules and requirements, the data available at that point in processing, and the application function modules available to update the application tables. It is important to search first for application modules that process the data and see if they can be called within the function exit. If the additional data in the extended segments in specific to a custom table or resides in nonkey fields of a single or small set of tables, you may be able to update it directly by SQL statements in the function exit. This approach should be carefully evaluated and is certainly not highly recommended.
Another option is to use Call Transaction from within the function exit to process the additional data. For example, in the case of message type WMMBXY for inbound goods movements from a warehouse management system, the standard interface creates batches for materials, but does not update its characteristics. In such a case, you can use Call Transaction MSC1 to create the batch and assign characteristic values to it from within the function exit provided.
Reward if Helpful

ERP5.0 to 6.0 upgrade-SAPup stuck after MAIN_SHDRUN/DDIC_UPG got canceled

Hi Experts:
We are currently upgrade SAP ERP 5.0 to ERP 6.0 EHP4 SR1 ABAP Based on SAP NW 7.0 eph1. During the upgrade, the SAPup process was canceled at MAIN_SHDRUN/DDIC_UPG phase of Preprocessing roadmap step by SIDadm. After that, it doesnu2019t allow user to continue or reset this step. The error message from SAPup.log is pasted below:
CURRENTPHASE MAIN_SHDRUN/DDIC_UPG
...started at 20110316230706
Reading Parameter File "C:\usr\sap\DEV\upg\abap\bin\APPEND.APP" at 20110316230706
...begin processing at 20110316233243
-> received signal Ctrl C from keyboard and exited at 20110317021613
...CANCELED at 20110317021613.
...CANCELED at 20110317021613.
Error message set: 'System error: Invalid access to memory location.
************************* SAPup started in UPGRADE mode *************************
This is SAPup version 7.10/7 patch level 31.022 compile time 01:28:19 Sep 3 2010.
This is UNICODE SAPup!
Running in graphics mode batch.
WARNING line 8029 in SYS file: Unknown id in line '4646     "20012" SFX;20110316233243;20110317021613;"";"C:
usr
sap
DEV
upg
abap
exe
:MY'
ERROR line 8030 in SYS file: Missing id in line '     "20012" SFX;20110316233243;20110317021613;"";"C:
usr
sap
DEV
upg
abap
exe
:MY'
Below is our system information:
Database: Microsoft SQL Server 2005   9.00.4035
Operating system: Windows Server 2003 R2, Enterprise x64 Edition SP2
Source System
Release: SAP ECC5.0
Kernel: 640 patch 247
R3trans version: 6400.364.18.43311
Tp version: 6400, 352, 18, 23218
Disp+work u2013V: 6400, 247, 15, 22555
Support Pack Level:
SAP_ABA     640     19     SAPKA64019     Cross-Application Component
SAP_BASIS     640     19     SAPKB64019     SAP Basis Component
PI_BASIS     2005_1_640     9     SAPKIPYJ69     Basis Plug-In (PI_BASIS) 2005_1_640
ST-PI     2008_1_640     0          -     SAP Solution Tools Plug-In
SAP_BW     350     19     SAPKW35019     SAP_BW 350
SAP_APPL     500     15     SAPKH50015     Logistics and Accounting
SAP_HR     500     5     SAPKE50005     Human Resources
EA-IPPE     300     4     SAPKGPIC04     EA-IPPE 300: Add-On Installation
PI     2004_1_500     14     SAPKIPZI6E     PI 2003_1_470 : Add-On Delta Upgrade
EA-APPL     500     5     SAPKGPAC05     SAP R/3 Enterprise PLM, SCM, Financials
EA-DFPS     500     5     SAPKGPDC05     SAP R/3 ENTERPRISE DFPS
EA-FINSERV     500     5     SAPKGPFC05     SAP R/3 Enterprise Financial Services
EA-GLTRADE     500     5     SAPKGPGC05     SAP R/3 Enterprise Global Trade
EA-HR     500     5     SAPKGPHC05     SAP R/3 Enterprise HR Extension
EA-PS     500     5     SAPKGPPC05     SAP R/3 Enterprise Public Services
EA-RETAIL     500     5     SAPKGPRC05     SAP R/3 Enterprise Retail
P3A     V500     7     SAPKIAF507     P3A V500 : Add-On Installation
ST-A/PI     01K_ECC500     0          -     Application Servicetools for ECC 500
Target System
Release: SAP ERP 6.0 Including Enhancement Package 4 Support Release 1 ABAP
            Based on SAP NetWeaver 7.0 Including Enhancement Package 1
Kernel: 701 32
R3trans version: 7010.129.18.43264
Tp version: 7010.124.18.35265
Upgrade type: High resource use (archive off)
Support Pack Level:
SAP_BASIS     701     0          -     SAP Basis Component
SAP_ABA     701     0          -     Cross-Application Component
PI_BASIS     701     0          -     Basis Plug-In
ST-PI     2008_1_700     0          -     SAP Solution Tools Plug-In
SAP_BW     701     0          -     SAP Business Warehouse
SAP_BS_FND     701     0          -     SAP Business Suite Foundation
WEBCUIF     700     0          -     SAP WEBCUIF 700
SAP_AP     700     0          -     SAP Application Platform
SAP_HR     600     0          -     Human Resources
EA-IPPE     400     0          -     SAP iPPE
EA-GLTRADE     600     0          -     SAP Enterprise Extension Global Trade
FINBASIS     600     0          -     Fin. Basis
EA-RETAIL     600     0          -     SAP Enterprise Extension Retail
EA-PS     600     0          -     SAP Enterprise Extension Public Services
EA-FINSERV     600     0          -     SAP Enterprise Extension Financial Services
EA-DFPS     600     0          -     SAP Enterprise Extension Defense Forces & Public Security
EA-APPL     600     0          -     SAP Enterprise Extension PLM, SCM, Financials
EA-HR     600     0          -     SAP Enterprise Extension HR
FI-CA     600     0          -     FI-CA
SEM-BW     600     0          -     SEM-BW: Strategic Enterprise Management
P3A     V604     4          -     P3A V604 : Add-On Installation
ST-A/PI     01M_ECC600     1          -     Application Servicetools for ECC 600
Would really appreciate it if anyone can help...

Hello Ling Lu,
this error points out to a corrupted MEMSAPehpi.dat file, probably when you terminated the session via Ctrl+C.
You must comment out the last line(s) of this file in order to proceed. Please open it and look for a repeated or incomplete last line(s) and comment it out. Make a backup of the file first, then repeat the phase, it should work.
Best regards,
Tomas Black

Error in installing SAP Netweaver 7.02

Hi all!
I'm new in SAP and installing the version 32-bit in Windows XP - SP2.
View the error bellow:
An error occurred while processing option SAP NetWeaver 7.0 including Enhancement Package 2 > SAP Application Server ABAP > MaxDB > Central System > Central System( Last error reported by the step :Path component contains reserved character (':'): C:)
What this is error?
Thanks.

Hi,
Check the path of DVDs defined for the installation process. Ensure that no blank spaces and special characters are present in the path.
Regards,
Deepak Kori

PI 7.1 including Enhancement Pack1

Similar Messages

Maybe you are looking for