Goods return best practice

Hi,
Kindly help me out in following senario
I raise a purchase order for 100 qty of goods at $2. I do a MIGO and receive all the quantity in to my Inspection stock (QM is activated). 80 items are OK and 20 not. So 80 of them are transfer posted to unrestricted stock and rejected 20 is transfer posted to restricted stock.
My question is what is the best practice SAP business process I need to follow in order to
1) return the rejected 20 back to the vendor and then
2) replace them with another 20 items from the same vendor?
3) what reports can I run to see the goods return information in SAP?

To answer the question :
1) return the rejected 20 back to the vendor and then
You can go to MIGO transaction, and choose "return delivery", and state the amount of money that will be returned
2) replace them with another 20 items from the same vendor?
Basically you can do several good receipts to a purchase order. So after you return delivery do a good receipt with reference to the same PO number
3) what reports can I run to see the goods return information in SAP?
What kind of reports do you want? if you want to see the material for each material document number, report using MB51 would be the best option. Either way, you can create a custom report for more specific kind of report
Hope it helps

Similar Messages

What is the best practice to manage versions in XI?

Hi!
Is there any <b>good</b> best practice ways to manage versions in XI.
Have a challenging scenario with many legacy systems and many interfaces per legacy system.
Should I put all the different interfaces for one legacy system under one namespace in the Integration Repository or should I make one own namespace for each interface.
Or is there other approaches, that I should consider to get a environment that is easily maintained.
br.samuli

Hi,
In our project we have defined our own naming conventions/namespaces.
For instance, we have agreed that we will group all interfaces (from all offices worldwide and different projects) into one single product version.
This global custom product will in turn be divided into different SWC (Software Components) and SWCV (Software Component versions).
So for each business scenario we will create separate SWC's and when necessary create new versions of these SWC's.
This means that each SWC should contain all the required objects to support a complete integration scenario i.e. inbound/outbound-interfaces, data types, msg types, business scenario's etc...
Regards,
Rob.

JMS / MBD Best Practices

Hello All,
There is currently a dispute in my camp about the limit of "responsibility" to place on a single MDB. In this case, the argument surrounds whether it is "good practice" to allow a MDB's onMessage function to:
- Open a connection to a servlet (the URL object obtained via Connection Manager via JNDI)
- Post some data
- Read the response and log it to local DB via JDBC
Firstly, is this too much responsibility for a single MDB?
Secondly, can someone please point me in the direction of some good MDB "Best Practices" documentation out there, free or otherwise.
I'm looking forward to settling this dispute.
Thank you all in advance.

Hi,
A MDB may become one of your application bottlenecks if it has to perform a time expensive operation. In such a case it may result of messages pilling up in your destination and dependent process blocking for an asynchronous event. But however, if your MDB work is isolated then its message throughput should not impact the overall application speed and can therefore be delegated expensive computation (assuming that the number of messages waiting to be processed is reasonable).
In your particular case, I would say that you should be ok assuming that your servlet doesn�t suffer too long downtimes. Depending of your expected traffic you will have to deploy the right number of servelet and MDB instances.
Hope this helps
Arnaud

General Oracle Database Performance trouble solving best practice Steps

We use Oracle 11g DB on Windows2008R2 as web application backend DB.
We have peformance trouble in that DB.
I would like to know General Oracle Database Performance trouble solving best practice Steps.
Is there any good general best practice document for performace trouble solving in the internet ?

@Girish Sharma: I disagree with this. Many people say things like your phrase "..first identify the root cause and then move forward" but that is not the first step. Any such technique is nothing more than looking at some report, finding a number that you don't like, and attempting to "fix" it. Some people use that supposedly funny term "compulsive tuning disorder" (first used by Gaja Krishna Vaidyanatha) to describe this approach (also advocated in this topic by @Supriyo Dey). The first step must be to determine what the problem is. Until you know that, all those reports you mentioned (which, remember, require EE plus pack licences) are useless.
@teradata0802, your best practice starts by finding the problem. Is it, for example, that the overnight batch jobs don't finish until lunchtime? A screen takes 10 seconds to refresh, and your target is one second? A report takes half an hour, but you need to run it every five minutes? Determine what business function is causing your client to lose money because it is too slow. Then investigate what it is doing, how, and why. You have to begin by focussing on the problem, not by running database-wide reports..

Return on Closed WO - Best Practice

Hi All,
We have a work order which is closed in Jan 2014. We have closed our accounting periods also. We need to do a reversal on this transaction. What is the best practice in industry? Thanks in advance.
Regards,
N

Is this a discrete job? I think it depends on what type of job and what the reason for the return is.
As you have probably realized by now, you are not able to re-open a closed wip job to perform a return transaction whether it is standard and non-standard.
If your job is non-standard, consider creeating a new non-standard to input reversals.
If your job is standard, is yuor item still in on hand, or has it been consumed by another assembly or by an order or project issue? Depending on what the answer to that is, what you do changes.
Different ways of accomplishing what you need, it depends on what type of return / the reason for the return.

Best Practices - Dynamic Ranking, Dimension Values to Return, etc.

The pinned post says non-technical questions belong on the Business Forum. I can't find an Endeca-specific business forum. If there is one, please tell me where to find it.
My question is about dynamic ranking and the initial display of only the top N dimension values with a "More..." option to see the rest of them.
What's the current wisdom on this from a usability point of view? Use it, don't use it? If using it, show how many values initially?
Or, if not using it, you instead set up a hierarchy of dimensions so that the user never has to look at 50 choices for something?
This is not a technical question. What is the current wisdom? What are the best practices?
Thanks!

Dynamic ranking is a good choice only if all choices cannot be further grouped. In my practice most of the content can be normalized and restricted to a very limited set of options. Dynamic ranking with "more" is an easy way out and seems like a lazy take on content management.

Is there a website or PDF somewhere which discusses best practices for producing a children's picture book? I am mostly interested in requirements for good image format, resolution, etc.

Is there a website or PDF somewhere which discusses best practices for producing a children's picture book? I am mostly interested in requirements for good image format, resolution, etc.

There may be a few links in Apple Support, regarding articles about how to use iBooks Author
and iBooks Store, etc; these would be separated into two general categories by device used.
Since there is an iOS and an OS X version of each, you may have to look to see what Apple
Support says about the one you are interested in; and how far their database goes toward an
answer to your question. Otherwise, a general search engine approach may be necessary.
Not sure if anything along the lines of what you seek would be available in an App.
References to iBooks Author and iBooks Store, etc appear within these two categories in Support:
For Mac OS X:
http://www.apple.com/support/mac-apps/
For iOS:
http://www.apple.com/support/ios/
Appears a community host moved your earlier post into one of the iBooks Author or Store sections
after I'd replied to what otherwise may be a similar post. Not sure if the links to the Discussions area
of iBooks you are interested in, have similar questions or answers by others who'd visited previously.
Is there a website or PDF somewhere which discusses best practices for producing a children's picture book? I am mostly interested in requirements for good image format, resolution, etc.
In my reply to your earlier thread, prior to it being moved, those links to sections of iBooks Author, etc
are posted. You can also find them from the main Apple Support Communities page.
Sorry to not be of much help in this matter.
Good luck & happy computing!

Temp Tables - Best Practice

Hello,
I have a customer who uses temp tables all over their application.
This customer is a novice and the app has its roots in VB6. We are converting it to .net
I would really like to know the best practice for using temp tables.
I have seen code like this in the app.
CR2.Database.Tables.Item(1).Location = "tempdb.dbo.[##Scott_xwPaySheetDtlForN]"
That seems to work, though i do not know why the full tempdb.dbo.[## is required.
However, when i use this in the new report I am doing I get runtime errors.
i also tried this
CR2.Database.Tables.Item(1).Location = "##Scott_xwPaySheetDtlForN"
I did not get errors, but I was returned data i did not expect.
Before i delve into different ways to do this, i could use some help with a good pattern to use.
thanks

Hi Scott,
Are you using the RDC still? It's not clear but looks like it.
We had an API that could piggy back the HDBC handle in the RDC ( craxdrt.dll ) but that API is no longer available in .NET. Also, the RDC is not supported in .NET since .NET uses the framework and RDC is COM.
Work around is to copy the temp data into a data set and then set location to the data set. There is no way that I know of to get to the tempdb from .NET. Reason being is there is no CR API to set the owner of the table to the user, MS SQL Server locks the tempdb to that user has exclusinve rights on it.
Thank you
Don

Best practice for searching on surname/lastname/name in Dutch

I'm looking for a best practice to store names of persons, but also names of companies, in my database.
I always store them as is (seems logical since you need to be able to display the original input-name) but I also want to store them transformed in some sort of way so I can easily search on them with LIKE! (Soundex, Metaphone, Q-Gram, ...)
I know SOUNDEX and DIFFERENCE are included in SQLServer, but they don't do the trick.
If somebody searches for the phrase "BAKKER", you should find names like "Backer", "Bakker", ... but also "De Backer", "Debecker", ... and this is where SOUNDEX fails ...
Does someone know some websites to visit, or someone already wrote a good function to transform a string that I can use to store the names but also to transform my search data?
(Example: (Pseudo lang :-))
function MakeSearchable (sString)
sString = sString.Replace(" ", ""); //Remove spaces
sString = sString.Replace("CK", "K");
sString = sString.Replace("KK", "K");
sString = sString.Replace("C", "S");
sString = sString.Replace("SS", "S");
return sString;
Greetz,
Tim

Thanks for the response, but unfortunately the provided links are not much help:
- The first link is about an article I don't have access to (i'm not a registered user)
- The second link is about Integration Services. This is nice for Integration stuff, but I need to have a functionality within a frontend.
- The third link is for use in Excel.
Maybe I'm looking for the wrong thing when wanting to create an extra column with "cleaned" up data. Maybe there's another solution from within my frontend or business layer, but I simply want a textbox on a form where users can type a search-value like
"BAKKER". The result of the search should return names like "DEBACKER", "DE BEKKER", "BACKER", "BAKRE", ...
I used to work in a hospital where they wrote their own SQL-function (on an Interbase database) to do this: They had a column with the original name, and a column with a converted name:
=> DEBACKER => Converted = DEBAKKER
=> DE BEKKER => Converted = DEBEKKER
=> BACKER => Converted = BAKKER
=> BAKRE => Converted = BAKKER
When you searched for "BAKKER", you did a LIKE operation on the converted column ...
What I am looking for is a good function to convert my data as above.
Greetz,
Tim

Best practice for dealing with Recordsets, JDBC and JSP?

I've spent the last three years developing web apps using JSP, Struts and Kodo JDO for persistence. All of the content for the apps was created as Java objects using model classes and saved to an Oracle db. Thus, data retrieved from the db was as instances of the model classes and then put into Struts form beans, etc.
I changed jobs last month and am now having to use Servlets with JDBC to retrieve records from db tables and returning it into Recordsets. Oh, and I can't use Struts in my JSPs either. I'm beginning to think that I had it easy at my previous job but maybe that's just because I was used to it.
So here are my problems/questions:
I have two tables with a one to many relationship that I need to retrieve data from, show in a jsp and be able to update eventually.
So here's what I am doing:
a) In a servlet, I use a SQL statement to join the tables and retrieve the results into a Recordset.
b) I created a class with a bunch of String attributes to copy the Recordset data into, one Recordset row per each instance of the bean and then close the Recordset
c) I then add the beans to an ArrayList and save the ArrayList into the session.
d) Then, in the JSP, I retrieve the ArrayList from the session and iterate over each bean instance, printing the data out to the jsp. There are some logic statements to determine when not to print redundant data caused by the one to many join.
e) I have not written the code to update the data yet but was planning on having separate jsps for updating the (one) table and the (many) table.
Would most of you do something similar? Would you use one SQL statement to retrieve all of the data for display and use logic to avoid printing the redundant part of the data? Or would you have used separate SQL queries, one for each table? Would you have saved the results into something other than an instance of a bean class that represents one record in the RecordSet? Would you have had a bean class with attributes other than Strings - like had a collection attribute to hold the results from the "many" table? The way that I am doing everything just seems so cumbersome and difficult compared to using Struts and JDO before.
Your help/opinion will be greatly appreciated!

Would you use one SQL statement to retrieve all of the data for display Yes.
and use logic to avoid printing the redundant part of the dataNo.
I believe in minimising the number of queries. If it is a simple one-many join on a db table, then one query is better than one + n queries.
However I prefer to store the objects in a bean class with attributes other than strings - ie one object, with a collection attribute to hold the related "many" records.
Does the fact you are not using Struts mean that you have to use scriptlet code? (shudder)
Or are you using JSTL, or other custom tags?
How about tools like Ant? Junit testing?
The way that I am doing everything just seems so cumbersome and difficult
compared to using Struts and JDO before.Anything different takes adjusting to. Sounds like you know what you're doing for the most part. I agree, in terms of best practices what you have described so far sounds like a step backwards from what you were previously doing.
However I wouldn't go complaining about it too loudly, too quickly. If you're new on the block theres nothing like making a pain of yourself, and complaining how backwards the work they have done is to put your new workmates' backs up
Look on it as a challenge. Maybe discuss it quietly with a team leader, to see if they understand how much easier/better/less error prone such approaches can be?
Struts, cumbersome as it can be, definitely has the advantage of pushing you to follow good MVC practice.
Good luck,
evnafets

Best practice - caching objects

What is the best practice when many transactions requires a persistent
object that does not change?
For example, in a ASP model supporting many organizations, organization is
required for many persistent objects in the model. I would rather look the
organization object up once and keep it around.
It is my understanding that once the persistence manager is closed the
organization can no longer be part of new transactions with other
persistence managers. Aside from looking it up for every transaction, is
there a better solution?
Thanks in advance
Gary

problem with using object id fields instead of PC object references in your
object model is that it makes your object model less useful and intuitive.
Taking to the extreme (replacing all object references with their IDs) you
will end up with object like a row in JDBC dataset. Plus if you use PM per
HTTP request it will not do you any good since organization data won't be in
PM anyway so it might even be slower (no optimization such as Kodo batch
loads)
So we do not do it.
What you can do:
1. Do nothing special just use JVM level or distributed cache provided by
Kodo. You will not need to access database to get your organization data but
object creation cost in each PM is still there (do not forget this cache we
are talking about is state cache not PC object cache) - good because
transparent
2. Designate a single application wide PM for all your read-only big
things - lookup screens etc. Use PM per request for the rest. Not
transparent - affects your application design
3. If large portion of your system is read-only use is PM pooling. We did it
pretty successfully. The requirement is to be able to recognize all PCs
which are updateable and evict/makeTransient those when PM is returned to
the pool (Kodo has a nice extension in PersistenceManagerImpl for removing
all managed object of a certain class) so you do not have stale data in your
PM. You can use Apache Commons Pool to do the pooling and make sure your PM
is able to shrink. It is transparent and increase performance considerably
One approach we use
"Gary" <[email protected]> wrote in message
news:[email protected]...
>
What is the best practice when many transactions requires a persistent
object that does not change?
For example, in a ASP model supporting many organizations, organization is
required for many persistent objects in the model. I would rather look the
organization object up once and keep it around.
It is my understanding that once the persistence manager is closed the
organization can no longer be part of new transactions with other
persistence managers. Aside from looking it up for every transaction, is
there a better solution?
Thanks in advance
Gary

Best Practice for Subcontracting without father

Dear All,
Can you throw some light on business case where we are sending some components to subcontractor but we are getting a service in return.
So when the work is finished we are doing service entry instead of parent material goods receipt.
What is the best practice to cater this business scenario?
Thanks in advance!

you can try this:
Use Account assignment category K, and Item category L. Don't enter material code , just enter the short text as the description of the service to be performed , enter the material group , give the cost center and enter the price.
At the item level, define the components
Normally, Item category L and acc. category K are not set together , but you can set this combination in OMG0 .
I havent tried this cycle, but if it works , it may meet your requirements in less steps.

What are best practice for packaging and deploying j2EE apps to iAS?

We've been running a set of J2EE applications on a pair of iAS SP1b for about a year and it has been quite stable.
Recently however we have had a number of LDAP issues, particularly when registering and unregistering applications (registering ear files sometimes fails 1st time but may work 2nd time). Also We've noticed very occasionally that old versions of classes sometimes find their way onto our machines.
What is considered to be best practice in terms of packaging and deployment, specifically:
1) Packaging - using the deployTool that comes with iAS6 SP1b to package is a big manual task, especially when you have 200+ jsp files. Are people out there using this or are they scripting it with a build tool such as Ant?
2) Deploying an existing application to multiple iAS's. Are you guys unregistering old application then reregistering new application? Are you shutting down iAS whilst doing the deployment?
3) Deploying ear files can take 5 to 10 mins, is this normal?
4) In a clustered scenario where HTTPSession is shared what are the consequences of doing deployments to data stored in session?
thanks in asvance for your replies
Owen

You may want to consider upgrading your application server environment to a newer service pack. There are numerous enhancements involving the deployment tool and run time layout of your application that make clear where you're application is loading its files from.
If you've at a long running application server environment, with lots of deployments under your belt, you might start to notice slow downs in deployment and kjs start time. Generally this is due to garbage collecting in your iAS registry.
You can do several things to resolve this. The most complete solution is to reinstall the application server. This will guarantee a clean ldap registry. Of course you've got to restablish your configurations and redeploy your applications. When done, backup your application server install space with the application server and directory server off. You can use this backup to return to a known configuation at some future time.
For the second method: <B>BE CAREFUL - BACKUP FIRST</B>
There is a more exhaustive solution that involves examining your deployed components to determine the active GUIDS. You then search the NameTrans section of the registry searching for Applogic Servlet *, and Bean * entries that represent your previously deployed components but are represented in the set of deployed GUIDs. Record these older GUIDs, remove them from ClassImp and ClassDef. Finally remove the older entries from NameTrans.
Best practices for deployment depend on your particular environmental needs. Many people utilize ANT as a build tool. In later versions of the application server, complete ANT scripts are included that address compiling, assembly and deployment. Ant 1.4 includes iAS specific targets and general J2EE targets. There are iAS specific targets that can be utilized with the 1.3 version. Specialized build targets are not required however to deploy to iAS.
Newer versions of the deployment tool allow you to specify that JSPs are not to be registered automatically. This can be significant if deployment times lag. Registered JSP's however benefit more fully from the services that iAS offers.
2) In general it is better to undeploy then redeploy. However, if you know that you're not changing GUIDs, recreating an existing application with new GUIDs, or removing registered components, you may avoid the undeploy phase.
If you shut down the KJS processes during deployment you can eliminate some addition workload on the LDAP server which really gets pounded during deployment. This is because the KJS processes detect changes and do registry loads to repopulate their caches. This can happen many times during a deployment and does not provide any benefit.
3) Deploying can be a lengthy process. There have been improvements in that performance from service pack to service pack but unfortunately you wont see dramatic drops in deployment times.
One thing you can do to reduce deployment times is to understand the type of deployment. If you have not manipulated your deployment descriptors in any way, then there is no need to deploy. Simply drop your newer bits in to the run time space of the application server. In later service packs this means exploding the package (ear,war, or jar) in to the appropriate subdirectory of the APPS directory.
4) If you've changed the classes of objects that have been placed in HTTPSession, you may find that you can no longer utilize those objects. For that reason, it is suggested that objects placed in session be kept as simple as possible in order to minimize this effect. In general however, is not a good idea to change a web application during the life span of a session.

Best Practice for Extracting a Single Value from Oracle Table

I'm using Oracle Database 11g Release 11.2.0.3.0.
I'd like to know the best practice for doing something like this in a PL/SQL block:
DECLARE
    v_student_id    student.student_id%TYPE;
BEGIN
    SELECT student_id
    INTO    v_student_id
    FROM    student
    WHERE   last_name = 'Smith'
    AND     ROWNUM = 1;
END;
Of course, the problem here is that when there is no hit, the NO_DATA_FOUND exception is raised, which halts execution. So what if I want to continue in spite of the exception?
Yes, I could create a nested block with EXCEPTION section, etc., but that seems clunky for what seems to be a very simple task.
I've also seen this handled like this:
DECLARE
    v_student_id    student.student_id%TYPE;
    CURSOR c_student_id IS
        SELECT student_id
        FROM    student
        WHERE   last_name = 'Smith'
        AND     ROWNUM = 1;
BEGIN
    OPEN c_student_id;
    FETCH c_student_id INTO v_student_id;
    IF c_student_id%NOTFOUND THEN
        DBMS_OUTPUT.PUT_LINE('not found');
    ELSE
        (do stuff)
    END IF;
    CLOSE c_student_id;
END;
But this still seems like killing an ant with a sledge hammer.
What's the best way?
Thanks for any help you can give.
Wayne

Do not design in order to avoid exceptions. Do not code in order to avoid exceptions.
Exceptions are good. Damn good. As it allows you to catch an unexpected process branch, where execution did not go as planned and coded.
Trying to avoid exceptions is just plain bloody stupid.
As for you specific problem. When the SQL fails to find a row and a value to return, what then? This is unexpected - if you did not want a value, you would not have coded the SQL to find a value. So the SQL not finding a value is an exception to what you intend with your code. And you need to decide what to do with that exception.
How to implement it. The #1 rule in software engineering - modularisation.
E.g.
create or replace function FindSomething( name varchar2 ) return foo.col1%type is
id foo.col1%type;
begin
select col1 into id from foo where col2 = upper(name);
return( id );
exception when NOT_FOUND then
return( null );
end;
And that is your problem. Modularisation. You are not considering it.
And not the only problem mind you. Seems like your keyboard has a stuck capslock key. Writing code in all uppercase is just as bloody silly as trying to avoid exceptions.

Best practice to create views

Hi,
I've a question about best practice to develop a large application with many complex views.
Typically at each time only one views is displayed. User can go from a view to another using a menu bar.
Every view is build with fxml, so my question is about how to create views and how switch from one to another.
Actually I load fxml every time the view is required:
FXMLLoader loader = new FXMLLoader();
InputStream in = MyController.class.getResourceAsStream("MyView.fxml");
loader.setBuilderFactory(new JavaFXBuilderFactory());
loader.setLocation(OptixController.class.getResource("MyView.fxml"));
BorderPane page;
try {
     page = (BorderPane) loader.load(in);
     } finally {
          if (in != null) {
               in.close();
// appController = loader.getController();
Scene scene = new Scene(page, MINIMUM_WINDOW_WIDTH, MINIMUM_WINDOW_HEIGHT);
scene.getStylesheets().add("it/myapp/Mycss.css");
stage.setScene(scene);
stage.sizeToScene();
stage.setScene(scene);
stage.sizeToScene();
stage.centerOnScreen();
stage.show();My questions:
1- is a good practice reload every time the fxml to design the view?
2- is a good practice create every time a new Scene or to have an unique scene in the app and every time clear all elements in it and set the new view?
3- the views should be keep in memory to avoid performace issue or it is a mistake? I think that every time a view should be destroy in order to free memory.
Thanks very much
Edited by: drenda81 on 21-mar-2013 10.41

>
>
My questions:
1- is a good practice reload every time the fxml to design the view?
2- is a good practice create every time a new Scene or to have an unique scene in the app and every time clear all elements in it and set the new view?
3- the views should be keep in memory to avoid performace issue or it is a mistake? I think that every time a view should be destroy in order to free memory.
In choosing between 1 and 3 above, I think either is fine. Loading the FXML on demand every time will be slightly slower, but assuming you are not doing something unusual such as loading over a network connection it won't be noticeable to the user. Loading all views at startup and keeping them in memory uses more memory, but again, it's unlikely to be an issue. I would choose whichever is easier to code (probably loading on demand).
In choosing between reusing a Scene or creating a new one each time, I would reuse the Scene. "Clearing all elements in it" only needs you to call scene.setRoot(...) and pass in the new view. Since the Scene has a mutable root property, you may as well make use of it and save the (small) overhead of instantiating a new Scene each time. You might consider exposing a currentView property somewhere (say, in your main controller, or model if you have a separate model class) and binding the Scene's root property to it. Something like:
public class MainController {
private final ObjectProperty<Parent> currentView ;
public MainController() {
    currentView = new SimpleObjectProperty<Parent>(this, "currentView");
public void initialize() {
    currentView.set(loadView("StartView.fxml"));
public ObjectProperty<Parent> currentViewProperty() {
    return currentView ;
// event handler to load View1:
@FXML
private void loadView1() {
    currentView.set(loadView("View1.fxml"));
// similarly for other views...
private Parent loadView(String fxmlFile) {
    try {
     Parent view = FXMLLoader.load(getClass().getResource(fxmlFile));
     return view ;
    } catch (...) { ... }
}Then your application can do this:
@Override
public void start(Stage primaryStage) {
   Scene scene = new Scene();
   FXMLLoader loader = new FXMLLoader(getClass().getResource("Main.fxml"));
   MainController controller = (MainController) loader.getController();
   scene.rootProperty().bind(controller.currentViewProperty());
   // set scene in stage, etc...
}This means your Controller doesn't need to know about the Scene, which maintains a nice decoupling.

Goods return best practice

Similar Messages

Maybe you are looking for