Change visible despite no release given

Hello,
I am using the ECR/ECO object to perform and monitor the change of objects - in this case BOMs.
I am not sure that the system behaves as designed so please chime in to tell me if it is standard or not.
Here are the steps I perform.
- I create an ECR and indicat a single object - a BOM and save it.
- I change the Status of the ECR to Check ECR
- I change the status of the object to Release possible
- I change the status of the ECR to ECR Checked, Approve ECR, Convert ECR
- I then give the change a validity date - say in two weeks time.
- I perform the change
I now create a production order such that the dates fall within the validity of the change request.
I am surprised too see that the change is being picked up!
I have not activated the 'complete change' or 'release change' status for the object, nor I have I activated the 'close ECO' or 'Release ECO' for the change header.
Is this normal behaviour? If it is, what is the point of the 'complete change' / 'release change' statuses?
Thanks for your thoughts.

hi
check the business transaction allowed for the status

Similar Messages

Change in Purchase Order Release Strategy Values

Dear All,
I am in process of changing Purchase Order release strategy values.
I have following release strategy -
                       Current Value                  (Proposed Value)
Level 1 -         Upto INR 0.1 Mn               (Proposed value - Upto 1.0 Mn)
Level 2 -         From 0.11 Mn to 0.5 Mn   (Proposed Value - From 1.01 Mn to 5.00 Mn)
Level 3 -         From 0.51 Mn to 1.0 Mn   (Proposed Value - From 5.01 Mn to 10.0 Mn)
Level 4 -         Above 1.0 Mn                  (Proposed Value - Above 10.0 Mn)
My questions are -
1) Will this change affect the existing Purchase Orders (already created) which are not yet released?
2) Will this change affect the existing Purchase Orders (already created) which are released?
3) Are there any risk factors?
Can you pl. put light on above questions?
Regards,
Prashant Kolhatkar

Hi,
Actually, what you had given is not enough to determine if the existing PO will be impacted or not
If you are just changing the classification but not changing the number of release level of the release code in the release strategy, the partial released PO will not be impacted unless there's PO changes. PO that are released will definitely not be impacted unless there are changed.
In general, after a release strategy is determined for PO, SAP will retrieve the latest list of release code of that release strategy for display for that PO. If this list never change (mean you only change classification of the release strategy), then they will not be apparent to the user. But if this list change (you add new release code, replace existing release code or remove release code), then you will see some discrepency on screen as you will only see the modified list of release code and not the old list of release code
Hope this help

Regarding passport registration issues, I need to have a letter from you including both the old and new imei numbers. Could you please send me an email mentioning that I have changed the phones with the given imei numbers?

Regarding passport registration issues, I need to have a letter from you including both the old and new imei numbers. Could you please send me an email mentioning that I have changed the phones with the given imei numbers?

You're not addressing Apple here. This is a user-to-user technical support forum. If you want to contact Apple, use the Contact Us link at the bottom right of every page for information on how to do so.
Best of luck.

Material number changed after purchase order released

Hi Experts
Please we are experiencing this behavior in our system.
A purchase order for a specific material number is created and released, after this we can change the material number and its plant ¿is this a standard and right be way of SAP?
Thank for your help
JM

Hi,
You can design your process as the business demand.You can set Release Indicator 1 in designing Release procedure for PO , where release Indicator 1 is used for purchasing document cannot be changed/Change not allowed after release.
Regards,
Biju K

Changing Purchase Reqs after release.

After releasing a Preq (Cost Centre), if we attempt to change it in ME52N everything on the line's display only. So I can't increase the qty for example and send for re-approval (trigger the release strategy). This is normal?
The Changeability indicator in OMGQ for the release indicator (F - released) was blank. I changed this to 4 but neither allow us to change the Preq after realease. Could you maybe advise please? Is it possible to change the req after release, seems odd I can't?

Hello,
in customizing for release indicator, you must check also field "Field selection key" which is defined under "Material management --> Purchasing --> Purchase requisition --> Define screen layout at document level". You should check the "Field selection key" assigned to your release indicator: that key defines the mandatory, optional and view-only fields in Purchase documents, and can be linked to a release status.
Hope to be useful.
Best regards,
Andrea

TS4550 6.1.3 is already out. Will this be changed in a point-release update to 6.1?

6.1.3 is already out. Will this be changed in a point-release update to 6.1?
My question is related to this KB article: http://support.apple.com/kb/TS4550?viewlocale=en_US&locale=en_US

nobody here would know. you'll hvae to wait and find out.

How I can change visible property of an af:table with an af:selectOneRadio?

How I can change visible property of an af:table with an af:selectOneRadio? Anyone can help me with a tutorial, example or link?
Thanks in advance.

After you add the required libraries to your classpath
you can do your use case as explained in this sample
page source
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<f:view xmlns:f="http://java.sun.com/jsf/core" xmlns:af="http://xmlns.oracle.com/adf/faces/rich">
    <af:document title="untitled2.jsf" id="d1">
        <af:messages id="m1"/>
        <af:form id="f1">
            <af:selectOneRadio label="radio" id="sor1" autoSubmit="true"
                               valueChangeListener="#{ControlVisibilty.onRadioSelected}">
                <af:selectItem label="0" value="0" id="si1"/>
                <af:selectItem label="1" value="1" id="si2"/>
            </af:selectOneRadio>
            <af:table value="#{bindings.DepartmentsView1.collectionModel}" var="row"
                      rows="#{bindings.DepartmentsView1.rangeSize}"
                      emptyText="#{bindings.DepartmentsView1.viewable ? 'No data to display.' : 'Access Denied.'}"
                      fetchSize="#{bindings.DepartmentsView1.rangeSize}" rowBandingInterval="0"
                      selectedRowKeys="#{bindings.DepartmentsView1.collectionModel.selectedRow}"
                      selectionListener="#{bindings.DepartmentsView1.collectionModel.makeCurrent}" rowSelection="single"
                      id="t1" partialTriggers="::sor1" visible="#{ControlVisibilty.table}">
                <af:column sortProperty="#{bindings.DepartmentsView1.hints.DepartmentId.name}" sortable="false"
                           headerText="#{bindings.DepartmentsView1.hints.DepartmentId.label}" id="c1">
                    <af:inputText value="#{row.bindings.DepartmentId.inputValue}"
                                  label="#{bindings.DepartmentsView1.hints.DepartmentId.label}"
                                  required="#{bindings.DepartmentsView1.hints.DepartmentId.mandatory}"
                                  columns="#{bindings.DepartmentsView1.hints.DepartmentId.displayWidth}"
                                  maximumLength="#{bindings.DepartmentsView1.hints.DepartmentId.precision}"
                                  shortDesc="#{bindings.DepartmentsView1.hints.DepartmentId.tooltip}" id="it1">
                        <f:validator binding="#{row.bindings.DepartmentId.validator}"/>
                        <af:convertNumber groupingUsed="false"
                                          pattern="#{bindings.DepartmentsView1.hints.DepartmentId.format}"/>
                    </af:inputText>
                </af:column>
                <af:column sortProperty="#{bindings.DepartmentsView1.hints.DepartmentName.name}" sortable="false"
                           headerText="#{bindings.DepartmentsView1.hints.DepartmentName.label}" id="c2">
                    <af:inputText value="#{row.bindings.DepartmentName.inputValue}"
                                  label="#{bindings.DepartmentsView1.hints.DepartmentName.label}"
                                  required="#{bindings.DepartmentsView1.hints.DepartmentName.mandatory}"
                                  columns="#{bindings.DepartmentsView1.hints.DepartmentName.displayWidth}"
                                  maximumLength="#{bindings.DepartmentsView1.hints.DepartmentName.precision}"
                                  shortDesc="#{bindings.DepartmentsView1.hints.DepartmentName.tooltip}" id="it2">
                        <f:validator binding="#{row.bindings.DepartmentName.validator}"/>
                    </af:inputText>
                </af:column>
                <af:column sortProperty="#{bindings.DepartmentsView1.hints.ManagerId.name}" sortable="false"
                           headerText="#{bindings.DepartmentsView1.hints.ManagerId.label}" id="c3">
                    <af:inputText value="#{row.bindings.ManagerId.inputValue}"
                                  label="#{bindings.DepartmentsView1.hints.ManagerId.label}"
                                  required="#{bindings.DepartmentsView1.hints.ManagerId.mandatory}"
                                  columns="#{bindings.DepartmentsView1.hints.ManagerId.displayWidth}"
                                  maximumLength="#{bindings.DepartmentsView1.hints.ManagerId.precision}"
                                  shortDesc="#{bindings.DepartmentsView1.hints.ManagerId.tooltip}" id="it3">
                        <f:validator binding="#{row.bindings.ManagerId.validator}"/>
                        <af:convertNumber groupingUsed="false"
                                          pattern="#{bindings.DepartmentsView1.hints.ManagerId.format}"/>
                    </af:inputText>
                </af:column>
                <af:column sortProperty="#{bindings.DepartmentsView1.hints.LocationId.name}" sortable="false"
                           headerText="#{bindings.DepartmentsView1.hints.LocationId.label}" id="c4">
                    <af:inputText value="#{row.bindings.LocationId.inputValue}"
                                  label="#{bindings.DepartmentsView1.hints.LocationId.label}"
                                  required="#{bindings.DepartmentsView1.hints.LocationId.mandatory}"
                                  columns="#{bindings.DepartmentsView1.hints.LocationId.displayWidth}"
                                  maximumLength="#{bindings.DepartmentsView1.hints.LocationId.precision}"
                                  shortDesc="#{bindings.DepartmentsView1.hints.LocationId.tooltip}" id="it4">
                        <f:validator binding="#{row.bindings.LocationId.validator}"/>
                        <af:convertNumber groupingUsed="false"
                                          pattern="#{bindings.DepartmentsView1.hints.LocationId.format}"/>
                    </af:inputText>
                </af:column>
            </af:table>
        </af:form>
    </af:document>
</f:view>The managed bean code is
import javax.faces.event.ValueChangeEvent;
public class ControlVisibilty {
    private boolean table;
    public ControlVisibilty() {
        setTable(false);
    public void onRadioSelected(ValueChangeEvent valueChangeEvent) {
        // Add event code here...
        if(valueChangeEvent.getNewValue().toString().equals("1"))
            setTable(true);
        else
            setTable(false);
    public void setTable(boolean table) {
        this.table = table;
    public boolean isTable() {
        return table;
}

[svn:bz-trunk] 20471: Changed visibility of start/ stopEndpoints methods from private to protected, so subclasses can override them.

Revision: 20471
Revision: 20471
Author:   [email protected]
Date:     2011-02-25 06:54:09 -0800 (Fri, 25 Feb 2011)
Log Message:
Changed visibility of start/stopEndpoints methods from private to protected, so subclasses can override them.
Modified Paths:
    blazeds/trunk/modules/core/src/flex/messaging/MessageBroker.java

Remember that Arch Arm is a different distribution, but we try to bend the rules and provide limited support for them. This may or may not be unique to Arch Arm, so you might try asking on their forums as well.

[svn] 3305: Change visibility of messageHandler(event:MessageEvent): void from private to protected.

Revision: 3305
Author: [email protected]
Date: 2008-09-22 17:44:38 -0700 (Mon, 22 Sep 2008)
Log Message:
Change visibility of messageHandler(event:MessageEvent):void from private to protected.
Bug: NA
QA: No
Doc: No
Checkintests Pass: Yes
Modified Paths:
flex/sdk/trunk/frameworks/projects/rpc/src/mx/messaging/ChannelSet.as

http://forum.java.sun.com/faq.jsp#format

Changes visible in BOM although ECM not released yet

Hi,
I have a BOM which has been updated together with a change number. The change number still has status "in work" and not released.
When I go to CS03, with all dates removed on the selection screen, I see the changes in there with the change number. That is ok with me, because then I expect to also see future changes in the BOM.
But when I go into CS03, with today's date in both date fields on the selection screen, I expect to see the old version of the BOM which should still be valid until the ECM is released. Not the changes done by this specific ECM. CS03 shows the BOM with the changes already in, and I think that is not correct. Why should the changes show when the ECM is not released?
Is this behaviour SAP standard or could there be a mistake in the customizing of the ECM status?
Any hint is useful.
Thanks,

Hi,
Though the status is set as "in work", the changes will be effected based on the valid from date maintained in change master CC01. You can practise putting a imaginary future date like 02.10.3333 on the valid from date in change master and when the change to be released change the valid from date as required.
You can also go through alternate date assignment in BOM.
Regards,
jyj9ja

Map.invoke & map.put change visibility question

Hi,
In the documentation is stated that changes done by a entryProcessor are visible only after the processor has finished execution. I could not find statement about the opposite direction - what happens if map.invoke() and map.put() are trying to change the same entry? Is there possibility the map.put method to be executed in parallel to the map.invoke, so that map.put changes value while map.invoke is being executed on it? I saw in the forum statement that all map operations are executed in single thread (when modifying the same entry)- does this mean that map.put is sort-of standard processor and is queued just like any other processors?
Best Regards,
Georgi

Hi Georgi,
all operations related to a single entry are executed in a single-threaded manner on the storage node, meaning either one or zero thread does anything on any single entry. It is not possible that a put would occur for an entry while an entry-processor is processing that entry.
And yes, it is a usable analog to think on a put operation as an entry-processor doing a setValue on the entry, or a lock/unlock operation as an entry-processor which changes the lock ownership (note: an acquired lock for an entry does not affect anything other than a lock operation for the same entry, which will not succeed until the earlier lock was released).
Best regards,
Robert

How to change visibility property of a VC iView by clicking of a BI iView?

Hi all!
I have created four iViews: two speedometers with web application designer and two iViews with visual composer. I added the speedometers and a visual composer iView #1 to a portal page (default view). The requirement is that by clicking the speedometer #2, the visual composer iView #2 would replace visual composer iView #1 on the portal page. If the user then would select the speedometer #1 again by clicking it, visual composer iView #2 would replace #1 again and so on.
I have read article http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/50b65a5d-f397-2910-a78a-f5544f21c33b?quicklink=index&overridelayout=true, but it is more about filtering VC iView values with BI web items. I don't need to filter anything, just to change one iView to another in a portal view by clicking a third one. How can I check what values my web application with Z_SERVICEOUTBOUND template is transfering to VC?
One solution might be¨to transfer any value to VC by clicking a speedometer and to change the visibility of the VC iViews according to that value (the speedometer #1 should in that case transfer other value to VC than speedometer #2). I don't know if that is possible with speedometers - you can't reference any characteristics or variables with it.
If you have an idea, what would be the best way to accomplish this requirement, I would be very glad to hear about it! We are in VC 7.0.
Points garanteed!
Regards
Sari

Hi
Since you are accesing the node containing the 'VISIBILITY' attribute you can use the following method to set the value
lo_el_visible->set_attribute(
exporting
name = `VISIBILITY`
value = 01 ). ""01 - none,02-visible
and remove this code
wd_context->set_attribute( EXPORTING name = 'VISIBILITY' value =
abap_false ).
Regards
Tamil
Edited by: Tamilselvan K on Aug 6, 2008 2:40 PM

Changes to a credit released document .

Hi Friends,
A sales order has been credit blocked and subsequently released. Later when we make any kind of change to the the order , would the order go for credit check again . The condition being the value in ' no of days, field in credit control config screen is
' 0' .
Regards
mahesh .

Hi,
The system does NOT carry out credit check again if the following conditions are met:
1.The value of the changed order is not greater than the value already approved for credit (inclusive of the deviation factor),
2.The current date is not greater than the original release date plus the number of days specified.
Regards,
MP

Change message status after release purchase order

Hi,
I'm a newbie in MM...
When a purchase order is created, the message status is not processed (yellow light) until the purchase order is released. Then the message is printed and the status changes to green light.
As far as I see, I can't find in the spro where is this customizing set or if there is a user-exit or badi for changing the message status depending on the release indicator.
Thanks in advance!
Jen

Hi Jen,
Complete the condition record, for example, like this:
- Transaction: MN04
- Output Type: NEU
- Choose third option: Purchasing Output Determination Document Type
- Document Type: NB
- Function: VN (Vendor)
- Medium: 1 (Print output)
- Date/Time: 4 (Send immediately (when saving the application))
Select the line and press button "Communication". Complete the output device and mark the option "Print immediately"
So, when the PO is created the system generates the message with yellow status. Then, when the PO is released, the message status will be green
Regards,
Fernando

Change visibility of table in interactive form through scripting

Hi all,
I am designing an interactive form in wd java. I used a table to display records in the interactive form.I want to make the table invisible if there is no data in the node. The table is wrapped in a subform . What scripting I need to do to make the table invisible if there is no data in the table node.
Thanks,
Satish Kumar

Dear Sathish,
I dont think there is direct way to control the visibility property in the Interactive form. Instead, you can create a table inside a subform and change the Subform Content Property to "Flowed".
You will be having a node assigned to the table. Instantiate the node twice, say first time for the heading row and the second time for the table content. and do this under the ciondition if the table is not enpty. This way you can control the visibility of the table and it is so simple.
if(<tablevalues> == null)
<Dont create any nodes>
else
//For Table Heading
IPrivate<>.ITestNode tn = wdcontext.nodeTest();
IPrivate<>.ITestElement tne = wdcontext.createTestElement());
tn.add(tne);
//For Table content
IPrivate<>.ITestNode tn1 = wdcontext.nodeTest();
IPrivate<>.ITestElement tne1 = wdcontext.createTestElement());
tn1.add(tne1);
Thanks,
Vivek.

Change visible despite no release given

Similar Messages

Maybe you are looking for