SRM Sap note 1633199 SRMi_CustomerConnectBusinessFunction

Sap note 1633199 >SRMi_CustomerConnectBusinessFunction
Category: Advance development
Primary Component: SRM-EBP-CA-UI User Interface/Templates
Any idea...what it is for? .... What is its purpose? What it enhance?
Would like to understand it moreu2026
We are planning to upgrade from 7.0 to 702 enhp.
It mentions u2026 create Business Function SRM_CONT_IMPR and create Customizing
u201CItu2019s due to Improvement request submitted by customeru201D
SRM_CONT_IMPR, SRM_700_SYSTEM_MSG SRM_700_SOURCING_SC_WFL, SRM_700_RFx_FROM_SC
Thanks
William

Hi William,
Please read about the details of the Switches here:
SRM, Continuous Improvement CC - Business Functions and Customizing Switches - SAP Library
Best regards,
Otto

Similar Messages

SAP Notes for Deleted Shopping Carts in SRM 7.02 in ECS

Hi ,
I am having an issue in SRM 7.02 in Extended Classic Scenario, Where Users are able to delete Shopping Carts even after Follow on Document created i.e. till Confirmation. Now they want to delete the SRM PO. As there is no Shopping Cart existing in SRM they are unable to delete the PO.
Can you please suggest me the SAP Note relevant to this Requirement.
Regards,
Raju.

Hello Raju,
check below KBA:
1649794 - Status dependent control of Shopping Cart
At the end of the KBA, OSS notes are listed. Check them.
Regards.
Laurent.

Mapping of Intercompany transaction between SRM & SAP R/3

Hi SRM gurus,
We have a scenario where the client wants intercompany transactions to be mapped between SRM & R/3.
i) they say according to interco transactions, using SRM PO, the following journal entry will be posted upon GRN:
                    Dr           Expense
                         Cr          A/P to Co Code 1 for SRM Vendor code
Question : if co code 1 recognizes A/R in Intercompany code, can we match the balance i.e : is it possible to recognize "A/P to Co Code 1 for SRM Vendor code" as Intercompany balance
ii) When Co. 1 pays for pdts / services on behalf of Co. 2, an intercompany, the journal entry will be as follows :
Co. 1 : Payment voucher (FB60)
a) on GRN :
                    Dr   Prepaid promotion
                          Cr    GR/IR Clearing
b) on IR :
                    Dr    GR/IR Clearing
                          Cr    A/P to Vendor
Co. 1 : Journal Entry (FB70)
Charge to Co. 2
                    Dr. A/R from Co. 2
                          Cr. Prepaid Promotion
Co. 2 : Journal Entry (MIRO)
On Invoice Recipt to Co. 1
                    Dr. Expense
                          Cr. A/P to Co. 1
Is it possible to make a set of journal entries as below by make config changes in SAP R/3 :
Co.2 :
Upon GRN : Dr Expense
                       Cr GR/IR Clearing
Upon IR :   Dr GR/IR Clearing
                       Cr A/P to Co.1
Co.1:
Upon IR :   Dr. from Co. 2
                       Cr. A/P to Vendor
The client wants to track the above postings scenario through old vendor code which is used as SRM vendor code and which is same as maintained in R/3 vendor master "Previous acct. no." field in Accounting view. To me the above entry on IR in R/3 is not at all feasible.
Like to have your expert suggestions on the above scenario how to map b/w SRM & SAP R/3.
Rgds,
Samik

Hi. What exactly are you looking for with the vendor material number? Note 444976 and 412817 are about it not transferring, butthey are very old, you have not said what version of SRM you are using.
For the goods receipt, I doubt there will be a note to let you set the posting date or document date in the backend based on approval date, but you can easily use BBP_DOC_CHANGE_BADI method BBP_CONF_CHANGE to set this date to whetever you want.
Regards,
Dave.

SAP Notes 488619 & 864481

Hi All,
has anyone tried to implement SAP Notes 488619 & 864481 for SRM 4.0 (SRM Server 5)?
These notes are supposed to correct the fact that the BAPI's for transferring Purchase Order data only transfer 22 characters for the Vendor Part Number, after applying these notes (and two other notes to R/3) then 35 characters should be transferred.
I get the following errors when trying to implement these notes
 Note 488619 - cannot add field VENDOR_MAT_LONG with component type
 IDNLF to structure BBPS_BAPIEKPOC as error message "Field
 VEND_MAT_LONG: Component type or domain used not active or does not
 exist" is generated.
 Note 864481 - the structure BAPIEKPOC which is described in the note
 does not exist in EBP nor does the component type LABNR.
Has anyone ever applied these notes? I've logged this with SAP but as the system version is old they claim it's charageable work.
Cheers
Chris

Hi
Please ensure you have done the following activities as mentioned in the SAP OSS Note - 488619.
1. Implement Notes 826541, 444770 and 455879.
2. First, check whether Note 864481 needs to be implemented in your system (this depends on the back end that you use).
3. For SRM 3.0 or lower, proceed as follows:
Call transaction SE11.
Enter structure "BAPIEBANV" as the data type and choose "Change".
Add field "VEND_MAT_LONG" to the structure and use component type "IDNLF".
Save and activate your changes.
Proceed in the same way for the following structures:
 BAPIEBANV
 BAPIEBAN
 BAPIEBANC
 BAPIEKPOC
 bbpekpoc46b
 bbpekpoc46c
 BAPIEKPO
Call transaction SE80.
In screen 3001 of function group "BBP_SC", replace field 'BAPIEBAN-VENDMAT' with field 'ITEMS-PARTNER_PROD'.
Save and activate your changes.
4. For SRM 4.0:
Call transaction SE11.
Enter structure "BBPS_BAPIEKPOC" as the data type and choose "Change".
Add field "VEND_MAT_LONG" to the structure and use component type "IDNLF".
Save and activate your changes.
5. For SRM 5.0:
Call transaction SE11.
Enter structure "BBPS_BAPIEKPO" as the data type and choose "Change".
Add field "VEND_MAT_LONG" to the structure and use component type "CHAR35".
Save and activate your changes.
Proceed in the same way for the following structures:
 BBPS_BAPIEKPOC
 BBPS_BS_RQ_ITEM_45B
 BBPS_BS_RQ_ITEM_46C
 BBPS_BS_RQ_ITEM_470
 BBPS_BS_PO_ITEM_45B
 BBPS_BS_PO_ITEM_46B
 BBPS_BS_PO_ITEM_470
 BBPS_BS_PO_ITEM_470_1
 BBPS_BS_PO_ITEM_ERP10
 BBPS_BADI_PO_ITEM_1
 BBPS_BADI_RQ_ITEM
 BBPEKPOC46B
 BBPEKPOC46C
Caution:
The structures that are specified in this note must be exactly the same in the EBP system as they are in the relevant back-end system. If the structures differ, adjust them. If you do not adjust them, it is very likely that the solution will not work. This means that you must also create fields that exist in the BAPI* structures in the relevant SRM structures.
6. Implement the correction instructions.
As mentioned in the SAP OSS Note 864481 - Changing struct 'BAPIEKPOC' of Release 4.6C and 4.7
Consulting Note. - After implementing note 626747 or applying Support Package SAPKH46C46 for R/3 46C or Support Package SAPKH47016 for R/3 470, structure 'BAPIEKPOC' is extended to a new field.
Make the following changes according to listed steps:
1. Add the following features to structure BAPIEKPOC using Transaction SE11 (Field 'Data type') after the last field:
2. For releases EBP3.0 and EBP3.5:
a) Component : PR_CLOSED
b) Component type: EBAKZ
3. For Releases EBP3.0, EBP3.5, EBP4.0, SRM 4.0, SRM 5.0:
a) Component : ACKNOWL_NO
b) Component type: LABNR
4. Save and generate the object.
Other related SAP OSS Notes to check out ->
Note 747132 APIs in BUS2105 and vendor's material number
Note 488619 Vendor's material numbers with more than 22 characters
Note 455879 BAPI_REQUISITION_CREATE BAPI_PO_CREATE: Vendor material
Note 827614 Vendor product number truncated with backend PO
Note 826541 BAPI_PO_GETDETAIL: Vendor material
Note 662300 BAPI_INFORECORD_GETLIST: VEND_MAT not complete
Note 892206 - SRM invoice: Enlarge Vendor product number to 35 chars
Note 887581 - SRM invoice: Vendor product number not transferred
Do let me know.
Regards
- Atul

Any SAP Note for RFC Error between BI and ECC 5.0

Hi..
the RFC Destination between BI and ECC 5.0 is giving errors.
Plz let me know if there is any Support pack or any solution to fix this error.
thanks..

Hi,
pls find the RFC connection details
1 Prerequisites
1.1 User Roles
Use
With the Building Block Connectivity a configuration role for each component is provided to access all transactions relevant for the installation. The following roles are available:
Technical name Description File name for upload
B02_01C B02 - Connectivity Configuration Role (SAP R/3) B02_01C.SAP
B02_03C B02 - Connectivity Configuration Role (SAP BW) B02_03C.SAP
C71_04C B02 - Connectivity Configuration Role (SAP CRM) C71_04C.SAP
B02_04C_SRM B02 - Connectivity Configuration Role (SAP SRM) B02_04C_SRM.SAP
Procedure
Please upload the necessary roles and add them to your user, using transactions PFCG (Role Maintenance).
2 Local Settings
This chapter describes all local settings that are necessary for each component like SAP R/3, SAP SCM, SAP BW, SAP CRM or SAP SRM.
2.1 SAP R/3
2.1.1 Define Client Administration (SAP R/3)
Use
This activity allows you to change Customizing settings.
Prerequisites
You have logged on to the system in English in order to start with the installation of the Best Practices Scenario.
Procedure
Run the following activity:
SAP R/3 Role Menu Define Client Administration (SAP R/3)
Transaction Code SCC4
SAP R/3 Menu Tools  Administration  Administration  Client Administration  Client Maintenance
Then carry out the following steps:
1. Choose Display  Change.
2. Confirm the warning message Caution: The table is cross client.
3. Select your SAP R/3 client and choose Details.
4. In the Change View Clients: Details screen, activate the following settings:
u2022 Automatic recording of changes
u2022 Changes to Repository and cross-client Customizing allowed
u2022 eCATT and CATT allowed.
5. Save.
6. Go back to the SAP Easy Access menu.
2.1.2 Defining a Logical System for SAP R/3 (SAP R/3)
Use
The purpose of this activity is to create a logical system for your SAP R/3 System. To enable communication between systems within your system landscape, you must
1. Define the systems as logical systems.
2. Assign the logical system for the SAP R/3 System to a client.
This enables the systems to recognize the target system as an RFC destination. If the logical system has already been created, skip this activity.
Logical systems are defined cross-client.
Procedure
Carry out the following steps:
1. Access the transaction using:
SAP R/3 Role Menu Defining a Logical System for SAP R/3 (SAP R/3)
Transaction Code SPRO
SAP R/3
IMG Menu Basis Components (for R/3 Enterprisse: SAP Web Application Server)  Application Link Enabling (ALE)  Sending and Receiving Systems  Logical systems  Define Logical System
2. Choose New entries.
3. In the column Log System, enter a name for the logical system that you want to create.
4. In the column Name, enter a description of the logical system.
Log. System Name
where XXX is the system name
and NNN is the client.
5. Save your entries.
A transport request for Workbench appears.
6. Select an existing request or create a new request, if necessary.
A transport request for Customizing appears.
7. Select an existing request or create a new request, if necessary.
2.1.3 Assigning Logical System to Client
Use
The purpose of this activity is to make an assignment for the logical system. Skip this activity if a logical system is already assigned to your client.
Procedure
Carry out the following steps:
1. Access the transaction using:
SAP R/3 Role Menu Assign Logical System to Client
Transaction Code SCC4
SAP R/3 Menu Tools  Administration  Administration  Client Administration  Client Maintenance
2. Choose Display ® Change.
3. Confirm the warning message The table is cross client.
4. Select your R/3 client and choose Details.
5. Enter the name of the logical system of your SAP R/3 client.
6. Save and confirm the warning message Be careful when changing the logical system.
7. Choose Back twice.
2.1.4 Creating an RFC User (SAP R/3)
Use
To enable communication between the SAP R/3 back-end system and the SAP SCM System, you have to create an RFC user in the SAP R/3 System.
The RFC user in the application client enables multiple RFC connections. Skip this activity if an RFC User has already been created.
Procedure
Carry out the following steps:
1. Access the transaction using:
SAP R/3 Role Menu Creating an RFC User (SAP R/3)
Transaction Code SU01
SAP R/3 Menu Tools  Administration  User Maintenance  Users
2. In the User field, enter RFCUSER.
3. Choose Create.
4. On the Maintain User screen, enter the following data on the Tab entry screens:
Address
Last Name
Function
Logon data
User type System
Password LOGIN
Profile
Profiles SAP_ALL
SAP_NEW
S_BI-WX_RFC
Defaults
Logon Language EN
5. Save your entries.
2.3 SAP BW
2.3.1 Define Client Administration
Use
This activity defines changes and transports of the client-dependent and client-independent objects.
Procedure
1. To perform this activity, choose one of the following navigation options:
SAP BW Role Menu Local Settings ® Define Client Administration
Transaction Code SCC4
SAP BW Menu Tools  Administration  Administration  Client Administration  Client Maintenance
2. Switch to change mode.
3. Select your client.
4. Choose details.
5. In field Currency enter the ISO-code of the local currency, e.g. USD or EUR.
6. In field Client Role enter Customizing
7. Check the settings for changes and transport of client-specific objects and client-independent object changes
If you want to use the settings made by BC-Sets or manually in other systems (other than BW), u201CAutomatic recording of changesu201D and u201CChanges to Repository object and cross-client Customizing allowedu201D is required.
Result
Client administration has been defined to support the installation using Best Practices.
2.3.2 Defining a Logical System for SAP BW (SAP BW)
Use
In this step, you define the logical systems in your distributed system.
Prerequisites
Logical systems are defined cross-client. Therefore cross-client customizing must be allowed in your client (this can be checked in transaction SCC4).
Procedure
To carry out the activity, choose one of the following navigation options:
SAP BW Role Menu Defining a Logical System for SAP BW (SAP BW)
Transaction Code SPRO
IMG Menu SAP Reference IMG  SAP Customizing Implementation Guide  SAP NetWeaver  Business Information Warehouse  Links to other Systems  General Connection Settings  Define Logical System
1. A dialog box informs you that the table is cross-client. Choose Continue.
2. On the Change View u201CLogical Systemsu201D: Overview screen, choose New entries.
3. On the New Entries: Overview of Added Entries screen enter the following data:
Field name Description R/O/C User action and values Note
Log. System Technical Name of the Logical System Enter a name for the logical BW system that you want to create
Name Textual Description of the Logical System Enter a clear description for the logical BW system
4. Choose Save.
If a transport request for workbench and customizing is displayed choose existing requests or create new requests.
If you want to continue with the next activity, do not leave the transaction.
Result
You have created a Logical System Name for your SAP BW client.
2.3.3 Assigning Logical System to Client (SAP BW)
Procedure
To carry out the activity, choose one of the following navigation options:
SAP BW
Role Menu Assigning Logical System to Client (SAP BW)
Transaction Code SCC4
SAP BW Menu Tools  Administration  Administration  Client Administration  Client Maintenance
1. In the view Display View "Clients": Overview, choose Display.  Change
2. Confirm the message.
3. Select your BW client.
4. Choose Details.
5. In the view Change View "Clients": Details, insert your BW system in the Logical system field, for example, BS7CLNT100.
6. Save the entries and go back.
2.3.4 Opening Administrator Workbench
Procedure
To carry out the activity, choose one of the following navigation options
SAP BW Modeling  Administrator Workbench: Modeling
Transaction Code RSA1
1. In the Replicate Metadata dialog box, choose Only Activate.
2. If a message appears that you are only authorized to work in client ... (Brain 009) refer to SAP Note 316923 (do not import the support package, but use the description under section Workaround).
2.3.5 Creating an RFC-User (SAP BW)
Procedure
To carry out the activity, choose one of the following navigation options:
SAP BW Role Menu Creating RFC User
Transaction Code SU01
SAP BW Menu Tools  Administration  User Maintenance  Users
Then carry out the following steps:
1. On the User Maintenance: Initial Screen screen:
a. Enter the following data:
Field Entry
User RFCUSER
b. Choose Create.
2. On the Maintain User screen:
a. Choose the Address tab.
b. Enter the following data:
Field Entry
Last Name RFCUSER
Function Default-User for RFC connection
c. Choose the Logon data tab.
d. Enter the following data:
Field Entry
Password LOGIN
User type System
e. Choose the Profiles tab.
f. Enter the following data:
Field Entry
Profiles SAP_ALL , SAP_NEW and S_BI-WHM_RFC
g. Choose Save.
Do not change the password of this user as it is used in RFC connections.
2.3.6 Define RFC-USER as default (SAP BW)
Procedure
To carry out the activity, choose one of the following navigation options
SAP BW Role Menu Define RFC-USER as default (SAP BW)
Transaction Code RSA1
SAP BW Menu Modeling  Administrator Workbench: Modeling
1. On the Administrator Workbench: Modeling screen choose Settings  Global Settings.
2. In the Global Settings/Customizing dialog box choose Glob. Settings.
3. On the Display View u201CRSADMINA Maintenance Viewu201D: Details screen:
a. Choose Display  Change.
b. Enter RFCUSER in the BW User ALE field.
c. Choose Save.
Hope this helps in solving u r problem
Regards
Ramakrishna Kamurthy

SAP Notes for installing ERP 6.0 EHP4 on NW 7.01 on IBM i 7.1

Hello members
The last time I install SAP on IBM i was about 3 years ago with ECC 6 on NW 7.00 on IBM i V5R4. Now, I have to install ERP 6.0 EHP4 on NW 7.01 on IBM i 7.1 for my new customer (only the ABAP ERP components - not CRM, SCM, SRM or Java stack). I try to first gather all important SAP notes that would be useful for me in doing the installation. By far, I identify note 1234455 (NetWeaver 7.0 EHP1/Business Suite 7 - IBM i) and 1432783 (Known Issued with IBM i 7.1). Is there any other notes I should be aware of for a successful installation?
I also need to identify the list of installation DVD that I need for this installation but, so far, I can identify DVD 51038620 (Install Master) and 51036902 (Install Export). I know I need more DVD than these two but I could not find any SAP notes that list all the DVD number I need.
Any suggestion would be very much appreciated?
Thanks.

Hello Satid,
nice to hear from you )
As you already pointed out, it is always useful, to read and apply the notes ...
What is special here ?
- Installation runs similar to your ecc6 stuff from 3 years ago - we typically replace the kernel of the kernel CD with a new patch level on the CD already.
- the big point is, that the system does NOT have EHP4 installed when you are done with SAPinst ;-(
you do have NW 7.01 and ERP6.00 => you have to start SAPEHPI immediately after that for all the components, that you require on EHP4. This is 95% of an complete upgrade => the installation is 2 . 3 times the effort of what wou would expect ...
If you do have questions, don't hesitate and contact us.
Regards
Volker Gueldenpfennig, consolut international ag
http://www.consolut.com http://www.4soi.de http://www.easymarketplace.de

Help How to Delta for ZBBPBW_DOCREL_SELECT - SAP Note 501836 / 931998

Dear Guru's,
We have applied the SAP Notes 501836 and 931998 in order to create the extractor mentioned above. In SAP note 501836 it mentions:
Note forSRM 4.0:
In SRM 4.0, the generic extraction also supports the delta update procedure. For you, this means that you can also use the delta update procedure for the extraction of the document flow.
Has anyone adopted or managed to make this extractor delta capable, if so could you please share how to achieve this.
Thanks and Kind Regards,
Alex

Hi Rana,
There is no need for you to set any thing for delta.
As normal run the IP with init with data transfer and then next enable delta for the next load.
Check for the Below matter which explains how the delta is carried in the case of FI data sources.
Financial Accounting line items are read by extractors directly from the tables in SAP R/3. A time stamp on the line items serves to identify the status of the delta data. Time stamp intervals that have already been read are stored in a time stamp table. The delta dataset is transferred to BW directly, without records being transferred to the delta queue in SAP R/3 (extractor delta method).
The Financial Accounting line items are extracted from SAP R/3 in their most recent status (after-image delta method). This delta procedure is not suitable for filling InfoCubes in BW directly. Therefore, firstly, the line items must be loaded in the BW system in an ODS object that identifies the changes made to individual characteristics and key figures within a delta data record. Other data destinations (InfoCubes, ODS objects) can be provided with data from this ODS object.
For more details check the below link
[Financial Accounting: Procedure for Line Item Extraction|http://help.sap.com/saphelp_nw70/helpdata/en/af/16533bbb15b762e10000000a114084/frameset.htm]
Regards
KP

SAP Note clarification

Hello Guys
I came through a SAP note that, in extended classic scenaio 'do not have the need to create SAP MM Purchase Requisition or Stock Reservation from the SAP SRM Shopping Cart''
Please let me know why.
Thanks in Advance.

Hello,
With Extended Classic Scenario, follow-on document for a Shopping Cart is always a Purchase Order.
This PO is first created in SRM, then replicated to the backend system. Reason why PO can be modified only in SRM system: you cannot edit corresponding PO in MM.
With Classic Scenario, follow-on document for a Shopping Cart can be:
- a Reservation,
- or a Purchase request,
- or a Purchase Order.
Those three kind of purchasing documents are always created in the backend system where you can modify them.
Regards.
Laurent.

Can you any one help to get the SRM - SAP Enterprise Buyer Troubleshooting

Hello Guys,
I am new to this SRM - SAP Enterprise Buyer Environment, I need to present troubleshooting idea to my higher level guys. Basically I am working in the area Basis.
Kindly help to get some useful documentation.
Thanks
Chilva.

hi,
i am sorry there is no documentation available for trouble shooting.
for Most of the problems , you have to check out the standard sap notes , sap help , configuration guides specific for srm.
thats what we used to when i was doing trouble shooting customer issues.
hope this helps.

SAP note 1045171

Hi All,
Currently when an admin places a shopping cart order on behalf of someone, the work flow is triggered for approval. And when the approver rejects it, the work item is returned to on-behalf-of person and not creator. We want to redirect the work item to SC creator instead of on-behalf-of.
We have implemented the SAP note 1045171 manually by using the correction instructions text file for the above mentioned requirement. But still the work item is being sent to the On-behalf-of (requestor) person. If anyone of you have previously implemented this SAP note, kindly give your inputs.
Thanks,
Divya.

Hi Divya,
Whenever a cart is rejected by an approver,is the work item going back to the cart creator in the normal scenario(Not BUY ON BEHALF)?
For workflows in SRM 7,there is an additional config when carts are rejected.
Please see the following link:
http://wiki.sdn.sap.com/wiki/display/SRM/EnablingWIreturningtotherequestorwhendocumentisfullyrejected
Please do the above config for you Shopping cart workflow and then check.Assuming all the changes of note 1045171 are implemented you should be fine.
Hope this helps.

SRM Oss Note Application - Activating Changes in Screens

Hello all,
I implemented oss note 1079525 at web dynpro for SRM 7.0 . I made changes at screens and codes according to the sap note.
But when i test my screens from explorer, i cant see the changes that i have done on screen. For example i added a field in selection screen but i cant see it on my SRM page.
I activate screens but do i have to publish it also?
Anyone has ideas or has done this before?
Thanks.

I hope you have done the below part from SAP Note and moved your changes to test client.
Meta data changes to be done in client 100(Customizing client)
Add a new entry in the view(sm30) /SAPSRM/V_MDF_HD with the following entries
Structure Field Name - CO_CODE
Bus. Object Type - BUS2201
Field Visible - X (YES)
Field Enabled - (NO)
Field Required- (NO)
***********Save the changes. Make sure that these changes are available in testing client before testing.

SAP System inconsistency for Inbound delivery / MIGO and a "sap note"

Hello Friends ,
After following SAP instruction on how to remove the inconsistency between posting GR through MIGO (Inv. mang.) and the reflection of the goods movement status in the inbound delivery document - done that using sap note 570991
the problem is that the system start behaving in a weird way throwing unjustified Error messages for any suggested goods receipt using MIGO with reference to inbound
for example after creating an inbound delivery document and trying to post it via migo , an error will pop up
- Inbound delivery storage location cannot be changed to here Message no. VLA316
the thing is i didn't even maintain any storage location entry up to that point and yet i cannot post any stock !!
also another error like
- Inbound delivery batch cannot be changed to *** here
which doesn't make any sense because there is not batches in the inbound document !!
i think this behavior is coming from the "Document Flow Update for Stock Postings" inbound indicator at the shipping parameter at client level customization
i need help on how to overcome this annoying SAP Bug/Problem specially i am in a post go live critical situation

Hi,
The messages you mentioned were introduced to avoid inconsistency between inbound delivery and IM, through the note: 1050944 - GR for inbound delivery using inventory mgmt as of ECC 6.00
If the messages are issued incorrectly, then you may check for SAP notes (I couldnt find anything relevant) or raise an OSS ticket to SAP.
Regards,
AKPT

How to revert back a SAP NOTE? Dump- Field symbol has not yet been assigned

Hi Experts,
We r getting dump(cause: Field symbol has not yet been assigned) in production for ABUMN tx, so, when debugged, it came to know that, the Field symbol is coming from REUSE_ALV_LIST_DISPLAY!!
So, for some reason the system message text is not getting output in ALV-->Dump!!
So, found a NOTE causing this problem!!
So, pls. let me know that, How to revert back this/any SAP NOTE? pls. in detail steps wise!!
thanq
Edited by: Srinivas on Jan 24, 2008 4:32 PM

Hi
In SNOTE tcode, select the Note that you implemented and click on 'RESET SAP Note Implementation'
shylesh

Sap note 1507799 - Sec 80CCD - pension contribution notified by central gov

Dear
I have applied the sap note 1507799 - Sec 80CCD - pension contribution notified by central govt. and have done the necessary manual config steps as mentioned in the sap note.
When i am trying to check this pension contribution notified by central govt item in IT0585 and IT 0586.
i am unable to get this item.
Regards
Vish

Hi ,
First do the manual changes & then apply the note. You will get "Contribution to pension scheme of Central Goverment" this option in IT 585
Regards,
Mahesh

Sap notes for 103 movement type and 105 movement types in sap

Hi all,
Please let me know if there are any sap notes for 103 movement type and 105 movement type in sap as soon as possible
points will be awarded.
thanking u in advance,
srinivas.

There are many SAP notes related to these movement types e.g 514609,750836,
533833, 808029, 317823,etc.
You can search them at http://service.sap.com
Regards,
Amit

SRM Sap note 1633199 SRMi_CustomerConnectBusinessFunction

Similar Messages

Maybe you are looking for