Email if Notification is created for the same material number

Hi,
IS it possible to get a email Automatically when a notification is created for the same material in last ___days/weeks.
Thanks
SM

Yes. Use the early warning system to send an eamil when ever the number of notifications exceeds a certain number in a given period time for a given group of objects.
You must have the info structures for QM in LIS activated for this to work.
Craig

Similar Messages

Adding quantity field for the same material number in Table control

Hello Experts,
I have an requirement, where I need to add the quantity field when the material number is repeated in a table control.
Here I show the pop-up message "Material already exists, do you want to add the quantity". If the user clicks on Yes I need to add the quantity.
I created the pop-up message using the FM " POPUP_TO_CONFIRM" and tried to add the quantity filed using COLLECT statement but I couldn't because my non-numeric field value will be different and it will insert new entry with same material in my internal table.
I have a z data base table & internal table with the below fields in it.
Best Regards,
Mani

hi deepthi,
chk a sample one which will help u. f4 hlp in table control
* Screen flow logic........
PROCESS BEFORE OUTPUT.
*MODULE PBO_MODULE.
PROCESS AFTER INPUT.
*MODULE PAI_MODULE.
PROCESS ON VALUE-REQUEST. "F4
FIELD EKPO-EBELP MODULE help_ekpo.
* populate screen field from within PROCESS ON VALUE-REQUEST(F4) call
*& Module help_responsibility INPUT
* text
MODULE help_ekpo INPUT.
**Transport values to table dynpro/screen table control
DATA: l_stepl LIKE sy-stepl,
 l_indx LIKE sy-stepl.
DATA: dynpfields LIKE dynpread OCCURS 5 WITH HEADER LINE.
* Adjust for scroling within table control
CALL FUNCTION 'DYNP_GET_STEPL'
 IMPORTING
 povstepl = l_stepl
 EXCEPTIONS
 stepl_not_found = 0
 OTHERS = 0.
l_indx = tc_ekpotable-top_line + l_stepl - 1.
 "tc_ekpotable should already have been declared
REFRESH dynpfields.
CLEAR dynpfields.
dynpfields-fieldname = 'EKPO-EBELN'.
dynpfields-fieldvalue = '00010' "wa_ekpo-ebeln.
dynpfields-stepl = l_stepl.
APPEND dynpfields.
dynpfields-fieldname = 'EKPO-EBELP'.
dynpfields-fieldvalue = '00020' "wa_ekpo-ebelp.
dynpfields-stepl = l_stepl.
APPEND dynpfields.
CALL FUNCTION 'DYNP_VALUES_UPDATE'
 EXPORTING
 dyname = 'SAPLZZ_EKKO' "Program name
 dynumb = '0100' "Screen number
 TABLES
 dynpfields = dynpfields
 EXCEPTIONS
 OTHERS = 0.
ENDMODULE. " help_ekpo INPUT
rgds
Anver
if hlped kindly mark points

How to Prevent/Control doing MIGO twice for the same material

Dear
The stores clerk by mistake has done MIGO twice for the same material. Is there any way to prevent/check the same in standard SAP? Vendor does not send the invoice/delivery challan to stores directly. Invoice is sent to Finance Department.
Regards

It is very unlikely that you could spec an ABAP solution to this problem.
You may be able to spec an exit that would prevent GR being carried out for a PO Item twice on the same day. But that is not infallible, as there may be valid circumstances when you would need to carry out two GR's for a PO item on the same day. A fix for a small problem that creates a large one is not a good fix.
You also need to ask how big this problem really is - if a user duplicates a goods receipt every once in a long while then you probably do not have a serious problem.
Rather than look at a system fix for the error, I would suggest that you look at what you can do to improve the physical process.

Sales Deal with two different validation dates for the same material

Hi SAPers,
I am trying to create a u201CSales Dealu201D VB31, for the same material/condition, but with two different validation dates. After the creation of the first record, I select u201CNew conditionu201D button, but the system give me the message VK104, u201Cthe condition is being processed in the current session.u201D.
How can I solve this issue?
Thanks in advance.
Pedro

We can't have multiple records for the same condition and key values valid on the same date. The condition end date is part of the primary key in the database table. The date ranges between the records cannot overlap. When you create a new record, usually the end date is set to 12/31/9999 by default. If you need to have this deal to end on a different date and a new deal to start afterwards, then first you need to change 12/31/9999 to a different date.
Also usually I try to exit the screen between the transactions.

In MIGO two seperate entry for the same Material in Accounting Document

Dear Expert,
Hi
Business is doing stock transfer transaction. Here with reference to stock transfer PO when business is doing Goods Issue.
here there is two stock transfer PO. in one PO there is two line items for the same material. in the second PO again same material with two line items.
but at the tme of Goods issue it is showing two seperate line for same material stock account credit in accounting document. but in the other Goods issue with reference to second PO it is showing only one line for inventory account credit in the accounting dcoument.
so pl. guide me on this.
thanks
H shah

Hi,
Step 1 : First we create the Stock transfer PO.
Step 2 : Goods issue with ref to above stock transfer PO ( Movement type 351) - MIGO
Step 3 : Goods Receipt with ref to above stock transfer PO ( Movement Type 101 )- MIGO
Thanks
H shah

Multiple info records for the same material record in the catalog

Hi Guys,
I have got sort of a puzzle I can not solve at the moment, maybe some one can help me to solve it. The situation in our system landscape is as follows:
Systems:
SRM 5.0 (Classic implementation scenario)
ECC 6.0
SRM-MDM 2.0
PI 2005
Material master is maintained in R/3 and the materials are replicated to SRM. From SRM we replicate all materials to the catalog repository in SRM-MDM.
As the material master in R/3 is vendor independent, the materials replicated to SRM also have no vendor attached. For the first initial material replication from SRM to the catalog SRM-MDM this also means that the products in the main table of the repository, u2018catalog positionsu2019, will not have a vendor or vendor number attached (i.e. no reference to a source of supply).
To assign a source of supply in the repository to a product (record) we will use info records which are replicated from R/3 to SRM-MDM. The mapping for this in the Import Manager can only be based on the product number. As this is the only unique value available which can map a info record to a already existing (but vendor less) ptoduct item in the catalog.
As long as every item in the repository has only one unique info record, meaning one source of supply with a specific price, there is no issue in the above scenario. Based on the product-id, the info record data will be matched with the material item in the catalog.
The issue for me arises when multiple info records exists for the same material. The info records can heave different vendors and different prices. All possible vendors should be available in the catalog for the same material (at least this is the requirement ).
At this point the product-id will no longer be an unique value. Importing the info records will cause problems, as only one material record is available in the repository for the specific product-id (remember that when doing a initial replication of the material master to the catalog, no vendor data is replicated).
Does anyone had this issue before, and knows a solution? Is it for example possible during the import of the info records in the Import manager, to duplicate material records in the destination data, based on the number of info records available in the source data for the same product-id. Or is there an other solution that I am missing?
Your help would be appreciated!
Regards,
Skander

Dear Poster
Your thread has had no response since it's creation over
2 weeks ago, therefore, I recommend that you either:
- Rephrase the question.
- Provide additional Information to prompt a response.
- Close the thread if the answer is already known.
Thank you for your compliance in this regard.
Jason Boggans
SAP SRM SDN Moderator

Different countries of origin for the same material

Hi All,
I need to maintain two different countries of origin for the same material, is this possible?
I have materials that are sold to customer in Europe and also in the US, but according to EU laws the country of origin is X and according to NAFTA laws the country of origin is Y.
I therefore need to be able to maintain the data according to the receiving country.
Is there a possibility to do this in SAP?
Thanks,
Sivan

Thank you for the answer.
The problem is not that I have a different vendor, but that I have a different customer. The laws regarding how to define the country of origin for the EU are a bit different from the laws regarding the US. Therefore the same material, purchased from the same vendor can have a different country of origin when we sell it to a customer in the US from the country of origin when we sell it to a customer in the EU.
I therefore need to maintain the country of origin according to the teratory in which the customer resides.
Do you know of a solution for this?
Thanks,
Sivan

Oracle Coherence*Web and BlazeDS: Multiple FlexSessions created for the same HttpSession

Hi all,
I have searched this forum and found a lot of good information from Alex Glosband and others about the infamous "Detected duplicate HTTP - based FlexSessions, generally due to the remote host disabling session cookies. Session coolkies must be enable to manage the client connection correctly." message.
It seems, however, none of the cases are identical to ours. This is ours:
- Resin 3.1.9
- Oracle Coherence 3.7.1 with Coherence*Web (session replication)
With this setup we get the "Detected duplicate HTTP..." message on the first attempt to use BlazeDS and on every subsequent call. The same client and server code works fine in a local sessions setup. With Coherence 3.3 (currently our production environment) it seems to occur less frequently, but still as frequent as it is a major issue for us. It fails even with a single node using in-process distributed caching in our test setup (as well as with multi node out of process caching in our staging environment, for Coherence knowledgeable the resin app server runs with tangosol.coherence.session.localstorage=true in the first case and false in the second).
Both the listener and message broker are mapped as "Coherence aware" in web.xml[1] so that they should use clustered sessions.
We have been digging a bit and we found out that if we commented out lines 427 and 434 of flex.messaging.endpoints.BaseHTTPEndpoint from version 4.0.0.14931 it seems to mask the bug. We added some logging in the setupFlexClient method and it seems that we get more or less a new FlexSession for each and every call - but they have the same cookie and thus underlying HttpSession. I.e. the list returned from flexClient.getFlexSessions() keeps growing. Thus we are not so keen on going to production with that memory leak and the above mentioned ugly hack of commenting out the detection of duplicates.
We use request scope for the remote object, but could in theory use any scope as we do not really have any state on the object itself, it is all HttpSession state and return values that are key (logon is performed prior to doing the first blaze call, in pure forms and ajax, and it is not a timing issue in that regard we are seeing).
Hope someone can shed some light on what can be happening. Is there any "reference testing"[2] or something when the FlexSessions are created that makes them being created as new? Where are they created? We do not know the inner workings of the BlazeDS source, we just watched the call trace of the unwanted invalidation and found that to be line 427 of flex.messaging.endpoints.BaseHTTPEndpoint.
Can we disable FlexSessions? Since the flex and plain html parts of the app share the sessions, we always use FlexContext.getHttpRequest().getSession() anyway, never storing any state directly in the FlexSession or on the remote object. Or maybe there is a config option to help us with this detection (or creation) of multiple FlexSessions?
Cheers and TIA,
-S-
[1] - For instance, this i the message broker servlet def:
<servlet>
<servlet-name>MessageBrokerServlet</servlet-name>
<display-name>MessageBrokerServlet</display-name>
<servlet-class>com.tangosol.coherence.servlet.api22.ServletWrapper</servlet-class>
<init-param>
<param-name>coherence-servlet-class</param-name>
<param-value>flex.messaging.MessageBrokerServlet</param-value>
</init-param>
<init-param>
<param-name>services.configuration.file</param-name>
<param-value>/WEB-INF/flex/services-config.xml</param-value>
</init-param>
<load-on-startup>1</load-on-startup>
</servlet>
[2] - As you undertstand this is speculation based on pure air, but it could be that in Coherence there was a serialization/deserialization happening somehow that would break such a test?

Just a quick update, it seems things are running in a stable fashion (and without visible memory leaks, just keeping the latest FlexSession) with these changes in BaseHTTPEndpoint:
 * Overrides to guard against duplicate HTTP-based sessions for the same FlexClient which will occur if the remote host has disabled session
 * cookies.
 * @see AbstractEndpoint#setupFlexClient(String)
 @Override
 public FlexClient setupFlexClient(String id) {
 log.debug("setupFlexClient start id " + id);
 FlexClient flexClient = super.setupFlexClient(id);
 // Scan for duplicate HTTP-sessions and if found, invalidate them and throw a MessageException.
 // A request attribute is used to deal with batched AMF messages that arrive in a single request by trigger multiple passes through this
 // method.
 boolean duplicateSessionDetected = (FlexContext.getHttpRequest().getAttribute(REQUEST_ATTR_DUPLICATE_SESSION_FLAG) != null);
 if (!duplicateSessionDetected) {
 List<FlexSession> sessions = flexClient.getFlexSessions();
 log.debug("Client has " + sessions.size() + " sessions.");
 int n = sessions.size();
 if (n > 1) {
 int count = 0;
 for (int i = 0; i < n; i++) {
 if (sessions.get(i) instanceof HttpFlexSession)
 count++;
 if (count > 1) {
 FlexContext.getHttpRequest().setAttribute(REQUEST_ATTR_DUPLICATE_SESSION_FLAG, Boolean.TRUE);
 duplicateSessionDetected = true;
 break;
 // If more than one was found, remote host isn't using session cookies. Kill all duplicate sessions and return an error.
 // Simplest to just re-scan the list given that it will be very short, but use an iterator for concurrent modification.
 int i = 0;
 if (duplicateSessionDetected) {
 List<FlexSession> sessions = flexClient.getFlexSessions();
 log.debug("Detected sessions from client: " + sessions);
 for (FlexSession session : sessions) {
 if (session instanceof HttpFlexSession && i < sessions.size()) {
// log.debug("----> sessionId: " + session.getId());
// Enumeration e1 = session.getAttributeNames();
// while (e1.hasMoreElements()) {
// Object key = e1.nextElement();
// log.debug("--------->" + key + "--------->" + session.getAttribute((String) key));
// session.invalidate();
 flexClient.sessionDestroyed(session);
 i++;
 // Return an error to the client.
// DuplicateSessionException e = new DuplicateSessionException();
// e.setMessage(ERR_MSG_DUPLICATE_SESSIONS_DETECTED);
// throw e;
 return flexClient;
It is not exactly beautiful (to say the least), but if it does the trick I might just be pragmatic enough to go with it... NB: I am of course not proposing this as a patch to this file or anything, it is just an ugly hack for our specific case, but maybe the information can help the BlazeDS team find the root cause making it incompatible with Coherence*Web.
Will give it a test run on our staging servers.

Spool no. not generating for the same shipement number

Hi,
I am working on shipment related forms. When i give the print of one shipment no., all the forms are going to one spool number. But my problem is when i take the same shipment number from second time onwards then all the forms are getting appended to the same spool number instead of creating a new spool number.
For example my shipment no.:- 1277489 contains 8 pages, when i take the same shipment no. for second time all the 8 pages getting appended and total 16 pages are going to that same spoll no. For third time 24 pages and 4th time 32 pages and so on... in the same spool request.
I have debugged the driver program, but i din't get any solution for that. So can any one suggest me of how to resolve this issue.
Thanks & Regards,
Ramana

Hi,
After selecting the print option, the print pop window appears. In that select the option New Spool Request.
Then give the print, it will come on new page.
You can also pass this option in the print program also. Pass TDNEWID = 'X' in parameter OUTPUT_OPTIONS.
Regards,
Vinod

Multiple BOM Explosion in MD04 for the same material

Dear PP Gurus,
Scenario is make to order. BOM is created for production usage (1) & sales usage (5) for a Header material. Routing also exists for the same.
Once i run MRP at plant level or material level after creating sales order , BOM is expoded multiple times i.e. 3- 4 times but proposals ( planned orders) are created as per requirements.But BOM explosion when we click on show overview tree is happening multiple times which should not happen.
Our client business is not getting hampered by this but still he doesnt want explosion multiple times and to be precise it should not happen.
Can anyone pls. throw some light on this .
Thanks in advance . Answers will be rewarded for sure.
regards,
Nagraj Vasmate

Hello Nagraj,
In MD04, On overview tree, it explodes all possible BOM for the header material.
System will explode all valid BOM's with usage 5 and 1 for that specific material.
Reg
Samson

2 deliveries created for the same sales order

2 Return Del docs & 2 credit notes were created for one return order no.
Posted: Apr 17, 2008 5:33 PM       E-mail this message      Reply
Dear SAP Support,
I would like to know why does the system created 2 return deliveries with the same qty for a single return order document no.? One return delivery doc.no. was created 2 mins earlier than the 2nd return delivery document no. on the same day. After these 2 return deliveries were created, a credit note was also created for each return delivery doc. number. Here is the document flow:
On Jan. 10, 2008, the Return Order was created
The Delivery block field is set to 90- (Return block)
The Billing block field is blank
On Jan. 14, 2008 @ 12:08:44, the 1st return delivery doc. no. was created. And on the same day also @ 12:10:44, the 2nd delivery doc. was again created. These 2 deliveries were created by 2 users. 1st delivery is by manual job, the 2nd is by background job processing. there was a 2 mins. interval for these 2 deliveries.
On Jan. 21, 2008 @ 9:47:33, the 1st Credit Return Note was created. And on the same day also @ 9:48:00, the 2nd Credit Return Note was again created.
In my initial investigation, I found out that there were changes made on the return order document before the 2 return delivery documents were created. Below are the changes that happened:
On Jan. 14, 2008, @ 9:25:22 hour, the following changes occurred:
a) Delivery block was changed from 90 - (Return block) to blank
b) Billing block was changed from blank to 08 - (check credit memo)
On Jan. 14, 2008, @ 12:08:44, T-Inv Comb field was changed from DC to C
On Jan. 21, 2008, @ 9:47:20, the Billing Block was changed again from 08 - (check credit memo) to blank
Will the above changes, contribute to this issue?
I am also suspecting that the timing on the creation of deliveries via manual job and scheduled background job processig could be the root cause because of the slim time frame between the two job?
I hope you can help me get an explanation to this and how this can be avoided.
Thank you very much in advanced for your help on this matter.
Hoping to hear from you soon.
Kind regards,
Cynthia M. Ondillo
SAP SD Functional Support

Hello Jonathan,
Yes, the 'update document flow' box is ticked and the entry in the 'Pos./negative quantity' field is '+'
Target delivery type is LR - Returns Delivery    Source sls doc. type is ZRE - Coats Returns Order
Item category is ZREN - Coats Returns Item
Since we do not see anything missing in the above setting, can we say that it is a system bug when running manual delivery job close to the time for running the scheduled background job?
If it is a system bug, how can this be corrected?
Regards,
Cynthia

Extractor 0CO_PC_PCP_03: diferent costing runs for the same material

Hi, experts.
We are extracting data with 0CO_PC_PCP_03 extractor, but some materials do not return any record.
If we use CO standard transactions, we can get the values for all materials, but with the extractor just few materials are returned.
We are filtering the extractor with the costing run name and costing run date, but some materials are not extracted.
This is occurring for a specific month only. We have extracted data for other months / costing runs and the same materials appears in CO transaction and in extractor result. The different thing with this problematic month is that there are other costing runs of the same type (costing variant), for a higher date.
It seems like the extractor just can extract the last costing run for a material / month. Any idea?
Thanks,
Henrique Teodoro

Hello,
I have an update in my findings. Few days ago, R/3 user ran a new costing run for a set of materials, using the same costing variant / costing version used one year ago. And now, when I extract the costing run created one year ago, materials present in recently run set don´t appear anymore. I ran this same costing run weeks ago and the material are ok. After the new costing run with the same costing variant / costing version, they are gone from extraction.
Seems like this extraction just can return the last costing variant / costing version for each material. Or maybe the table key that stores this data are costing variant / costing version, instead of costing run / costing run date.
Anybody have any knowledge or experience on this?
Thanks,
Henrique

Consignment vs owned inventory for the same material/inventory (cycle count)

Hi All,
I am looking at ways within SAP that I could differentiate materials/inventory that are consignment and owned inventory...
We have a department that are experiencing difficulties performing cylce counts as they both owned and consignments parts and materials and it is currently done manually.
Is there a way for us to generate a single inventory that includes both owned and consignment in the same report?
Any help would be great!
Cheers!
Wendell

Hi Wendell,
If you have batch management and WM, this should not be a problem.. In this case, you should be able to identify where each batch is located and if the batch is consignment or own.
If not, then execpt you separate the inventory in different storage locations, the inventory could be mixed.
Anyway, I recommend you to move this thread to SAP MM:
SAP ERP - Logistics Materials Management (SAP MM)
Kind Regards,
Mariano

Auto GR for the same material and with different routings to diff stor loc

Hi All,
I have a semi finished material having 2 different routings line 1 and line 2 and with respective 2 different storage locations but need to have Auto GR.

I'm not sure what you are asking; to cause an operation to do auto GR, you need to choose the right operation control key. The auto GR is controlled via the operation control key.
Then for the Slocs; on the production version (MRP 4 view) you have a field "receiving location". Maintain for each of the two versions the right location.
Next, create a new production order, and choose one of the production versions. Release, and do CO11N for the operation with the auto GR control key. See that it is received in the desired Sloc..

L_TO_PREPARE_ITEM_INT batch split for the same material

Hello Gurus,
I use L_TO_CREATE_MULTIPLE to create TO.
if I leave empty charg number for one material line in FN VB_BATCH_DETERMINATION that is triggeredc in L_TO_CREATE_MULTIPLE batches are determined (without quantities) but I thought it is prepared for eventual batch split
But I suppose not as I have a problem when I put quantity greater that quantity on one batch the functionality L_TO_PREPARE_ITEM_INT does not split material into batches, does it mean that I need to split this quantity on batches before calling L_TO_CREATE_MULTIPLE or maybe something in customizing is missing?
Bests Bogumila

Hi,
I had a also used this FM.
When you pass the total quantity it will only return the batch which should be used first to fulfill your requirement.
So you have to keep this FM in a Loop and keep subtracting the proposed quantity and store it in a Internal table till it is zero.
Thanks
Ajay

Email if Notification is created for the same material number

Similar Messages

Maybe you are looking for