BAPI_GOODSMVT_CREATE for all expired Materials changed to blocked from rest

here are my requirements
The current functionality in SAP takes a Material and changes it from Unrestricted to Restricted at the time of Material Expiry.
The Following Functionality is required:
Upon automatically running a batch job the system will check for all expired Materials with a stock status of Restricted and change that status to Blocked
i have to call Call 'BAPI_GOODSMVT_CREATE' function module for creating the material document
Upon running Batch job, the program will look in table MCH1 for all Batch/Material combinations that have an expired SLED (field: VFDAT).
After finding all expired Batch/Material combinations in step one the program will then use that data to locate the associated Plants (field: WERKS) and Storage Locations (field: LGORT) in table MCHB
where BAPI2017_GM_CODE-GM_CODE = 04(Transfer Posting).
my question is after passing the selcted data into GOODSMVT_ITEM will the materials that i have selcted will automatically be changed from Restricted and change that status to Blocked
id so what would be the correct GOODSMVT_ITEM-MOVE_TYPE
please help

Similar Messages

Max stock level and reorder point for all the materials

Dear experts,
Is there any standard mm report that will give the details of max stock level and reorder point details for all the materials?
Thanks in advance,
Regards,
Krish

Your requirement can be pulled from table MARC. I dont think there is a standard report to meet your requirement. You can meet your requirement through SAP Query though.

Reg storage location for all the materials in the plant.

Dear Gurus,
In my plant I would like to know the storage location for all the materials in the plant.can u guys suggest me the solution?

If Stock is there in Each Storage Location then You can Run MMBE Report by Inputting Material & Plant. Then it will Show All the Storage Location Stocks for a Plant.
Or you can Run MM60 Report Which will give you Detail Report.
Else you Can Check in MMSC List of Extendable Storage Locations.
Regards,
Ashok

Need to checks if ASN has been received for all the materials in the

Hi Experts,
Can you please give me an idea
I need checks if ASN has been received for all the materials in the Invoice.
what filed do i need to check.
Regd's
Vardesh,

Hi Jagadeeswari,
If you need to check Workflow Trace check Transaction SWU9. This displays all the WOrkflow started on a particular time period we specify. Check Program RSWTTR01 and also table SWT_LOGCAT which could help you. The transaction i have specified displays all the Workflow that has been executed and whether it is been a success or a failure.
Hope this would help you.
Thanks,
Prashanth

How to use for all entires clause while fetching data from archived tables

How to use for all entires clause while fetching data from archived tables using the FM
/PBS/SELECT_INTO_TABLE' .
I need to fetch data from an Archived table for all the entries in an internal table.
Kindly provide some inputs for the same.
thanks n Regards
Ramesh

Hi Ramesh,
I have a query regarding accessing archived data through PBS.
I have archived SAP FI data ( Object FI_DOCUMNT) using SAP standard process through TCODE : SARA.
Now please tell me can I acees this archived data through the PBS add on FM : '/PBS/SELECT_INTO_TABLE'.
Do I need to do something else to access data archived through SAP standard process ot not ? If yes, then please tell me as I am not able to get the data using the above FM.
The call to the above FM is as follows :
CALL FUNCTION '/PBS/SELECT_INTO_TABLE'
EXPORTING
    archiv           = 'CFI'
    OPTION           = ''
    tabname          = 'BKPF'
    SCHL1_NAME       = 'BELNR'
    SCHL1_VON        = belnr-low
    SCHL1_BIS        = belnr-low
    SCHL2_NAME       = 'GJAHR'
    SCHL2_VON        = GJAHR-LOW
    SCHL2_BIS        = GJAHR-LOW
    SCHL3_NAME       = 'BUKRS'
    SCHL3_VON        = bukrs-low
    SCHL3_BIS        = bukrs-low
SCHL4_NAME       =
SCHL4_VON        =
SCHL4_BIS        =
    CLR_ITAB         = 'X'
MAX_ZAHL         =
tables
    i_tabelle        = t_bkpf
SCHL1_IN         =
SCHL2_IN         =
SCHL3_IN         =
SCHL4_IN         =
EXCEPTIONS
   EOF              = 1
   OTHERS           = 2
   OTHERS           = 3
It gives me the following error :
Index for table not supported ! BKPF BELNR.
Please help ASAP.
Thnaks and Regards
Gurpreet Singh

Broker wait for all receiver to acknowledge before returning from publish()

Does the broker wait for all receiver to acknowledge before returning from publish()?
If suppose i had 10 subscribers. I observerd 10th subscriber getting message late. I thought publisher will wait for acknolodge for each subscriber ? else why it getting message late ?

I assume you are questioning why the subscriber's onMessage() is getting
called way after the publisher's publish() had returned.
The JMS publishers only know that it is sending msgs to a destination.
Whether there are 0 or 100 subscribers to the destination is something it
doesn't know or care about.
The message is sent to a destination on the broker first and then it is
delivered to the subscribers of the destination.
The publisher's publish() method will not return until the message has
been successfully delivered (and persisted if necessary) to the broker.
Note that this does not mean that the message has been successfully
received by any subscribers.

"Date Modified" for all files being changed if "Automatically write to XMP" is on

Recently upgraded from LR3 (v3.4.1) from LR2 on OSX 10.6.8 and have always had Catalog Settings > Automatically write changes into XMP turned on.
When browsing existing JPG files in my Library (no Develop changes, no keywording, no Presets, no Import), LR3 is writing to disk — i.e., when I look at files in Finder, almost every viewed file’s “Date Modified” is being set to today’s date and time. (It actually creates a .swp file, then changes it's name back to .jpg)
This is really bad, as it's making it impossible for me to use Finder to figure out when I last worked with a file, it is triggering needless Time Machine and Backblaze backups, and unnecessarily churning my disk.
If I turn off "Automatically write..." this behavior stops. Per David Marx at thelightroomlab.com, I tried turning off this preference, manually doing a "Save Metadata to File" for all files, letting that complete, then turning the preference back on. This does not solve the problem.
Per a suggestion at photoshop.com, I used ExifTool to see what changes LR was writing to a sample file; from the diff below, you can see that LR is adding a bunch of new fields as well as moving other fields around. But my point is that LR3 should never overwrite a file on disk if all I am doing is browsing thru them.
Is anyone else seeing this? Any ideas would be greatly appreciated!
-- David
diff Exif5609_original Exif5609_update
2c2
< FileName: DSC_5609_original.JPG
> FileName: DSC_5609_update.JPG
5,6c5,6
< FileModifyDate: 2009:11:27 21:32:54-08:00
< FilePermissions: rwxr-xr-x
> FileModifyDate: 2011:08:07 22:06:47-07:00
> FilePermissions: rw-r--r--
27a28,29
> ShutterSpeedValue: 1/200
> ApertureValue: 7.1
55d56
< SerialNumber: 3209521
75d75
< Lens: 18-200mm f/3.5-5.6
185,188d184
< UserComment:
< SubSecTime: 00
< SubSecTimeOriginal: 00
< SubSecTimeDigitized: 00
211a208,299
> XMPToolkit: Adobe XMP Core 5.2-c004 1.136881, 2010/06/10-18:11:35
> CreatorTool: Ver.1.00
> MetadataDate: 2011:08:07 22:06:47-07:00
> SerialNumber: 3209521
> LensInfo: 18-200mm f/3.5-5.6
> Lens: 18.0-200.0 mm f/3.5-5.6
> ImageNumber: 26634
> RawFileName: DSC_5609.JPG
> SavedSettingsName: Import
> SavedSettingsType: Snapshot
> SavedSettingsParametersVersion: 6.4.1
> SavedSettingsParametersProcessVersion: 5.0
> SavedSettingsParametersWhiteBalance: As Shot
> SavedSettingsParametersIncrementalTemperature: 0
> SavedSettingsParametersIncrementalTint: 0
> SavedSettingsParametersExposure: 0.00
> SavedSettingsParametersShadows: 0
> SavedSettingsParametersBrightness: 0
> SavedSettingsParametersContrast: 0
> SavedSettingsParametersSaturation: 0
> SavedSettingsParametersSharpness: 0
> SavedSettingsParametersLuminanceSmoothing: 0
> SavedSettingsParametersColorNoiseReduction: 0
> SavedSettingsParametersChromaticAberrationR: 0
> SavedSettingsParametersChromaticAberrationB: 0
> SavedSettingsParametersVignetteAmount: 0
> SavedSettingsParametersShadowTint: 0
> SavedSettingsParametersRedHue: 0
> SavedSettingsParametersRedSaturation: 0
> SavedSettingsParametersGreenHue: 0
> SavedSettingsParametersGreenSaturation: 0
> SavedSettingsParametersBlueHue: 0
> SavedSettingsParametersBlueSaturation: 0
> SavedSettingsParametersFillLight: 0
> SavedSettingsParametersVibrance: 0
> SavedSettingsParametersHighlightRecovery: 0
> SavedSettingsParametersClarity: 0
> SavedSettingsParametersDefringe: 0
> SavedSettingsParametersHueAdjustmentRed: 0
> SavedSettingsParametersHueAdjustmentOrange: 0
> SavedSettingsParametersHueAdjustmentYellow: 0
> SavedSettingsParametersHueAdjustmentGreen: 0
> SavedSettingsParametersHueAdjustmentAqua: 0
> SavedSettingsParametersHueAdjustmentBlue: 0
> SavedSettingsParametersHueAdjustmentPurple: 0
> SavedSettingsParametersHueAdjustmentMagenta: 0
> SavedSettingsParametersSaturationAdjustmentRed: 0
> SavedSettingsParametersSaturationAdjustmentOrange: 0
> SavedSettingsParametersSaturationAdjustmentYellow: 0
> SavedSettingsParametersSaturationAdjustmentGreen: 0
> SavedSettingsParametersSaturationAdjustmentAqua: 0
> SavedSettingsParametersSaturationAdjustmentBlue: 0
> SavedSettingsParametersSaturationAdjustmentPurple: 0
> SavedSettingsParametersSaturationAdjustmentMagenta: 0
> SavedSettingsParametersLuminanceAdjustmentRed: 0
> SavedSettingsParametersLuminanceAdjustmentOrange: 0
> SavedSettingsParametersLuminanceAdjustmentYellow: 0
> SavedSettingsParametersLuminanceAdjustmentGreen: 0
> SavedSettingsParametersLuminanceAdjustmentAqua: 0
> SavedSettingsParametersLuminanceAdjustmentBlue: 0
> SavedSettingsParametersLuminanceAdjustmentPurple: 0
> SavedSettingsParametersLuminanceAdjustmentMagenta: 0
> SavedSettingsParametersSplitToningShadowHue: 0
> SavedSettingsParametersSplitToningShadowSaturation: 0
> SavedSettingsParametersSplitToningHighlightHue: 0
> SavedSettingsParametersSplitToningHighlightSaturation: 0
> SavedSettingsParametersSplitToningBalance: 0
> SavedSettingsParametersParametricShadows: 0
> SavedSettingsParametersParametricDarks: 0
> SavedSettingsParametersParametricLights: 0
> SavedSettingsParametersParametricHighlights: 0
> SavedSettingsParametersParametricShadowSplit: 25
> SavedSettingsParametersParametricMidtoneSplit: 50
> SavedSettingsParametersParametricHighlightSplit: 75
> SavedSettingsParametersSharpenRadius: +1.0
> SavedSettingsParametersSharpenDetail: 25
> SavedSettingsParametersSharpenEdgeMasking: 0
> SavedSettingsParametersPostCropVignetteAmount: 0
> SavedSettingsParametersGrainAmount: 0
> SavedSettingsParametersLensProfileEnable: 0
> SavedSettingsParametersLensManualDistortionAmount: 0
> SavedSettingsParametersPerspectiveVertical: 0
> SavedSettingsParametersPerspectiveHorizontal: 0
> SavedSettingsParametersPerspectiveRotate: 0.0
> SavedSettingsParametersPerspectiveScale: 100
> SavedSettingsParametersConvertToGrayscale: False
> SavedSettingsParametersToneCurveName: Linear
> SavedSettingsParametersCameraProfile: Embedded
> SavedSettingsParametersCameraProfileDigest: D6AF5AEA62557FCE88BC099788BBD3CC
> SavedSettingsParametersLensProfileSetup: LensDefaults
> SavedSettingsParametersToneCurve: 0, 0, 255, 255
> IPTCDigest: d41d8cd98f00b204e9800998ecf8427e
228,230d315
< SubSecCreateDate: 2009:11:27 21:32:54.00
< SubSecDateTimeOriginal: 2009:11:27 21:32:54.00
< SubSecModifyDate: 2009:11:27 21:32:54.00
http://feedback.photoshop.com/photoshop_family/topics/lr3_date_modified_for_all_files_bein g_updated_when_browsing_photos_if_catalog_settings_automatically_write_changes_into_xmp_is /replies/6313647

clvrmnky wrote:
davidpope007 wrote:
Then when LR3 loaded my old LR2 images into memory, it "dirtied" the in-memory copy of the file by adding in these new LR3 XMP fields. Then, because I had "Automatically write XMP" on, it said "I better write these changes to disk".
Yuck. As a former software engineer, this is very bad software engineering.
It should wait until the user dirties the file (via Develop, keywords, etc.) before presuming to add a bunch of metadata fields that are unique to the new version of LR3.
Well, I'm a current software developer, and this is, really, a perfectly reasonable thing to do. It is a reasonable trade-off for a convenient feature required by a small subset of users.
Yes, in most cases the in-memory copy should "never" be dirtied unless the user makes a gesture of some sort, but like I said earlier, this option (once set by the user) sets up the situation where this gesture becomes implicit. This is a clear trade-off for the sake of convenience. And if the XMP is out of date and needs to be updated en masse, so be it.
The fact is, there is no easy way around this. Do we save up /every/ dirty buffer somehow until you make a gesture that /might/ require the XMP to be up-to-date before acting on that gesture? Now we have to worry about unflushed buffers if something goes wrong and the app exits. Do we save the buffers to the DB? Now we have to block some calls to make another blocking call to flush some or all of those to DB, and then write some or all of it out to one or more files. In what order? What if there is a gesture to have X files with up-to-date XMP and some or all of those are in unflushed buffers, unflushed DB writes or we have to wait for the DB.
As you can see, this is a transactionality nightmare, and the easiest and safest thing to get what the user wants (i.e., up-to-date XMP for the purpose of talking to a third-party XMP aware app) is to simply update the sidecar or XMP block in an atomic manner using the correct file IO. The file will have to change at some point, so it may as well be now.
[Thanks to both of you for your detailed replies. I am aware of the need for tradeoffs so when you say the approach taken is quite reasonable, I do believe you. I also apologize in advance for the length of the following and am extremely aware of the time it must have taken you to compose the above replies, but I'm going to add a bit more, if only for my own piece of mind and in hopes of coming up with a solution for my workflow.]
From my naive point of view, I was expecting the answer to be simply "don't raise the XMPDirtyFlag upon reading in a file". Obviously if your architecture requires you to "upgrade to latest XMP format" upon read, and another part of the system auto-detects "out of date XMP", then it's going to write those changes to disk.
But it didn't need to be designed that way. LR obviously has mechanisms to know when a user has made a change to XMP so it is able to write XMP changes to disk only when necessary.
The promise (to me) of "Automatically Write XMP changes to disk" was to auto-save my changes, and not those made for any internal (i.e., XMP versioning related) changes.
Perhaps the premise is that it is LR3's job to update an individual file's XMP to the latest version so that other XMP-aware apps can make use of it? I would argue that those third-party XMP-aware apps already have to know how to deal with all prior versions of XMP, so LR3 should just leave well enough alone.
You asked if my problem with your approach was that it was "inelegant"; not at all, it is based on my own perception of what I need from my workflow, so let me describe that so maybe we can find a better way:
* Part of the appeal of LR to me is that it preserves my original file as it came off the memory card, allowing me to move to a different workflow/toolset in 2025 if I choose to do so
* However, with all of changes contained in a single database file, I'm concerned about rare (but possible) corruption, so to mitigate this risk, I let LR backup my database weekly and it's also backed up continuously in the cloud via Backblaze
* Even with backups of the database, there is still a chance that I could lose changes made to individual files (e.g., LR corrupts the DB and I have to go back to last week's DB)
* Thus the appeal of the "auto-write to XMP" flag -- that way critical changes (develop, crop, keywords) are saved on a per-file basis; I liked the "automatic" part of this (as opposed to a manual save) because then I don't have to teach others in my family how to manually save XMP changes
* A nice side-effect of this setting is now when I use Finder to find a file and double-click on it to edit it in Photoshop, all my develop changes are right there; (in other words, I like the flexibility of not having to fire up LR in order to just invoke PS from within it); also when I use Bridge I see all the keywords there
* So with LR2, I had gotten used to what I thought was the best of all worlds -- autosave of changes at the file level via XMP + raw negatives untouched (i.e., Date Modified == the date I took the picture); this allows me to use operating-system-level tools -- Finder -- to locate/search for files
* Now I upgrade to LR3 and I'm finally now understanding that a concept "XMP versioning" is going to result in changes to many, but not all my files. (That's something else that's annoying about this issue -- I open up the Grid and browse a folder of files, and only seemingly random ones I've cursored over seem to get written to disk -- if it's so urgent that LR3 update the XMP, then it should do it for all the files in the catalog or at least in that directory)
Here's a screenshot from Finder of what I see everytime I look at this folder:
* So now I have to assume that each new version of XMP and/or LR is going to touch my files on disk. Sigh.
* What I don't like about this is that it is ruining the promise of "untouched raw negative". Yes, the image data is untouched -- which I agree is most of the benefit; but the file has been touched.
* Perhaps you might empathize a bit more if you imagined that someone went thru all your source code or Word files and randomly changed the date to "today" because you upgraded compilers or moved to Word 2011.
I agree all of this would be solved by having an XMP sidecar file for JPGs, but you indicate that's not going to happen.
You've also alluded to the solution of "resetting the Date Modifed" to it's original value -- which I believe is what Finder does when you move or copy a file -- but that that is fraught with issues as well. I believe you when you say there are issues, but again the naive part of me wonders why that soultion would be so bad...
I just thought of another potential solution -- turning on Date Created in Finder -- but it turns out that's changed, too.
I am really at a loss as to what to do and would welcome your suggestions.
Thanks again and kind regards,
-- David

One PR for all raw materials

Hi,
Is it possible that after MRP run we get only one Purchse requisition for all the raw materials.
I will try to explain
Suppose we have a finished product F1 and R1 , R2 and R3 are three raw materials required to produce F1.
Now in a normal case when we take MRP run for F1 we get three PRs for R1, R2 and R3.
But is it possible to get only one PR which will contain R1, R2 and R3 as line items (As we have in Purchase Orders) in it.
Regards
Abhi

Abhi,
At PR level it is not possible, but the workaround is that you can use the automatic PO using PR transaction (ME59N) to consolidate multiple PR into a single PO. There are certain prerequisites to be met for this,
1. Vendor should be defined for Automatic PO, Materail Master Purchase view Auto PO to be activated.
2. Inforecord for the material.
3. Source list with fixed vendor and MRP relevant indicator needs to be maintained.
with the above set of defination after MRP run Vendor gets assigned automatically to PR and you can use transaction "ME59N" to consolidate multiple PR's to a single PO.
You can also run program "RM06BB30" to create PO's in background based on the selection critera given in the intial screen....
I hope this would satisfy your need....Reward your points and close the thread,
Regards,
Prasobh

How do I set the about:config settings for all users? iprism keeps prompting from authentication for users.

When users log on and try to open Firefox 23.0.1, users are prompted with Iprism Authentication. We made changes to the firefox about:config values "network.automatic-ntlm-auth.allow.-non-fqdn" and "Network.negotiate-auth.allow-non-fqdn" to true and it works, but only works on a per user basis. How can we set this up for all users?

I would think the about:config entries discussed are ex-factory set to values each user has to change individually, after the installation has run its course. The solution could be to have patched files ready to install post factum:
[https://developer.mozilla.org/en-US/docs/Mozilla/Preferences/A_brief_guide_to_Mozilla_preferences A Brief Guide to Mozilla Preferences - MDN]

My background color for all pages has changed to pink, how do I get it back to white?

The background color in all of my screens has switched to pink. How do I get it back to white? I wonder if it changed when I was shopping in a web site and had clicked on a pink watch(?)

Check the default color settings:
*Tools > Options > Content : Fonts & Colors > Colors
* [X] "Allow pages to choose their own colors, instead of my selections above"
*https://support.mozilla.com/kb/Changing+fonts+and+colors

Release strategy retrigger for all non significant changes

HI,
My client has the below requirement:
The Purchase requsitions and Purchase orders are released by different approval authorities. Any change made to any field like material short text, cost centre, payment terms, material long text, etc. the sytem has to cancel all the previous releases and release strategy need to be retriggred from the beginning.
I request all to provide me with an user exit or badi if any available in the system to achieve this.
Regards,
Rayeesuddin

Dear Ray,
First discuss this with your functional consultant (MM) from functional point is there is any setting.
Regards,
D.Srinivas.

Use This Thread for All 3rd Party Extension Questions (Migrating from v3-v4)

This thread is for the 3rd Party Extension developers as they update their extensions to be compatible with the new framework in SQL Developer v4.0.
To get started with the process, consult this post from the JDeveloper team. If you have questions, post them here.

What is the correct way to deploy migrated extension on local installation of SQL Developer 4 for testing?
Could such operation be automated with help of JDeveloper 12c?

Material Ledger Status for exisitng materials change

Hi,
What is the best way to perform material ledger closing entries for pre-existing materials in plant?
I have a plant that already has pre-exisiting materials since 01/2009 or prior, and then we activated material ledger for this plant.
Of course, we then try to run actual costing CKMLCP for these existing materials for period 05/2010, and is errored with
"carry-out period-end closing for materials in previous period" message. I try OSS note 361236 to close out periods that are older than previous period..with the MMPV period shift situation; but is not helping because these materials are already existing, so I can have CKM3 analysis for these materials as far back as 01/2006...as I ran report S_ALR_87013180 to check the period status for all these materials to see how far do i have to go back in terms of period/fiscal yr.
My question is, if there are pre-existing materials active in the plant and then we activated ML, how far do I have to go back to get the CKMLCP done? Or what is the best way to handle such scenarios?
any advice?

Hey,
Can you let me know when did you do the ML startup?
At production start, the system automatically sets all materials to price determination control 2, which will not be included in ckmlcp processing.
And when you change the price determination from 2 to 3 via CKMM, the period status will be automatically changed to "new object", for which there's no need to do the period end closing.
Anyway, if your materials is with status 30 for the previous periods, the most convenient solution is to manually set it to 70 for the last period. You may achieve this via program MLHELP_SET_PP_STATUS_70. You only need to do it for the period before last period. Then you can go ahead with the normal period end closing process for the previous period.
Best Regards
Young

Changing shared variable reference modes for all nodes in application. Shortcut?

I have a large application which makes extensive use of both network-published and single-process shared variables. I want to change the reference mode of every such node in the application from absolute to target-relative. Is there any way to do this without having to open every subVI in the application and use the right-click menu on every node?
Sean

I don't know of any shortcut, but if you want to change the reference node of everything in the application you could probably script it. I was thinking something similar to what I have below where you traverse the BD of a specific VI for all SharedVariableNodes and change the relative mode to Target Relative.
Depending on how your project is organized you can add some additional functionality before the open VI reference to go through and open the reference of every VI in your project.
Matt J
Professional Googler and Kudo Addict
National Instruments

Changes like password and removal of roles for all users

Hi
i want to change password for all users and remove single roles from all users.When i am doing this in SU10 changes are not reflecting for users.Please help reg this
Vinod

Me too...I have never been able to remove roles from multiple users with SU10. I don't know if it's a bug or (more likely) just a confusing screen, but in 4.7 it never worked for me.

BAPI_GOODSMVT_CREATE for all expired Materials changed to blocked from rest

Similar Messages

Maybe you are looking for