Decentralized WM and Hu's

Hello:
We are implementing DWM, as we are testing the IDOC's, creating them manually. As the WM will be no SAP.
I found that the system is asking for a HU in the Inbound delivery, but the configuration of the Item Category in the delivery Item, does not require packing, neither the storage location in the Delivery.
Does anybody know why a HU is being required?, are HU mandatory when operatin with DWM.
If I enter a HU, I can post the GR, but this is not how we want to operate.
Thanks in advance.

Hi,
We use DWM as well and we use HU Management at Storage Location Level. But as per your scenario, HU is not really required to do a PGR. Check your packing control settings at Storage type and Movement type levels as well.
Good Luck,
Thanks
Vinod.

Similar Messages

Goods Receipt in Decentralized WMS

Dear Friends
Our client processes the GRN by creating a Inbound delivery for PO, Then MIGO with movement type 107 for the inbound delivery and then MIGO with 109.
Now do i process the Stock putaway in Decentralized WMS since i understand that inbound delivery is replicated in the Decentral WMS and the subsequent confirmation is done in central system upon the confirmation of TO.
The requirement is that the process of putaway in the decentral WMS must be started after MIGO -109.
Please advise me on this. Your help shall be greatly appreciated
Thanks

Hi Anand,
What is the main idea for the 107 and 109? Why don't you create the PO with stock type "S" and then take the stock to your WH in this stock mode? When the goods are cleared/released you do a migo 343 to transfer the stoc kfrom block to unrestricted?
I checked out the process with 107 (where the PO has an sloc which is linked to the DWM sloc) and this is not possible.
Is this in special cases or for all inbound materials?
Regards,
Hein

Ageing wise vendor and customer report

hi....
Where i can get ageing wise vendor and customer report?
Thanks & Regards
Rekha shrama

Hello
First configure credit management & customise.
A/R Summary
Degree of ageing
You can set the allowed degree of ageing in Customizing for Sales, under Basic Functions ® Credit Management/Risk Management ® Credit Management ® Define Automatic Credit Control.
Under Checks in financial accounting/ old A/R summary, you can enter the permitted degree of ageing for the A/R summary, in the fíelds Permitted days and Permitted hours. Here, you can define how old the A/R summary can be, in order to be called up for a check. If the permitted degree of ageing for the A/R summary is exceeded in the credit check, then the document is blocked.
Fields allowed days and allowed hours are only available for entry if you have entered an X in field Read A/R Summary in Customizing. The path is: Accounts Receivable and Accounts ® Credit Management ® Credit Control Account ® Make basic settings for credit management.
Updating
The A/R summary is either sent periodically (with the help of the report RFCMCRCV) from central Financial Accounting to the decentralized Sales and Distribution units according to ALE distribution model or, if an obsolete A/R summary is presented, updated for the credit check by the system per remote function.
In order that the system is burdened as little as possible, SAP recommends you stick to the following order:
Program run: Incoming payments in central FI
Program run: Distribution A/R summary from central FI to decentralized Sales and Distribution units
Program run: Renewed credit check for blocked sales documents in decentralized Sales and Distribution units
Status Management for Obsolete A/R Summary
If the A/R summary is obsolete, the credit status Credit data obsolete is set. This means that the document is blocked, and appears in the credit representativeu2019s worklist. In Customizing for Sales, in the section Automatic Credit Control, for the single, aforementioned checks, for which FI data is necessary, you can define whether a warning appears in the obsolete data, or whether a status is set.
If you are working with the A/R summary, and would like to re-process obsolete data, it is recommended that you set a status.
Reg
suresh

Decentral Adapter not showing up in RWB

I have just installed a J2ee Decentral Adapter instance, configured the exchange profile to connect back to the main PI instance and connected it to the SLD (both the J2ee Decentral Adapter and main PI instance use the same SLD).
One of the last steps is to check see if the Decentral Adapter shows up in the PI Instances Runtime Work Bench (RWB), but it does not.
I've noticed that on the SLD, the J2ee Decentral Adapter shows up as a Technical System, but when going to the SLD > Administration > Content Maintenance > All Instances > Class: XI Adapter Framework, that only my main PI instances show up, not the recently installed J2ee Decentral Adapter.
Anybody have any ideas of what else to check ?
Thanks..SB

Aaron,
1.1 SAP XI AF CPA Cache are set at the defaults of the install. The SLDAccess is set to true which according to the following SAP Help doc says that the entris are ignored: http://help.sap.com/saphelp_nw04s/helpdata/en/29/22ee41c334c717e10000000a155106/frameset.htm
1.2 SLD DATA Supplier is set correctly. I can do a CIM Test and trigger the data upload successfully. Still no entry under the Content Maintenance though.
2. SXI_CACHE > Adapter Engine still does not show the Decentral Adapter. I've even bounced both systems and the SLD.
per Chirag I've also double checked blog "Basic Steps In Decentralized Adapter Engine
This Decentral adapter is in DMZ #1, so I must use the IP of my SLD for the SLD access and my Main PI is in DMZ #2. I've checked to make sure ports 50000 and 3300 from Decentral to my PI system work - are there any other ports ?
Thanks...Scott B.

Warehouse number from "Decentralized WMS" to "Centralized"

Hi all
We have implemented a warehouse number with Decentralized WMS.
ERP and WM are SAP systems.
Now, weu2019d like to integrate WM into the same ERP SAP system (convert a warehouse number from "Decentralized WMS" to "Centralized").
So, what shall we do?
Can we maintain the same warehouse number and do the customizing on it (deactivate Decentralized WMS and so on)? Or we must define a new one?
In both cases, (maintain the same warehouse number or define a new one) how can we transfer WM stock from decentralized to centralized?
Any suggest?
Thanks a lot
Michele

Hi Funky Tech.
Thank you for your answer, but my question is another.
We have already implemented a warehouse number as decentralized WMS.
Now we want to integrate it into ERP (centralized WMS).
So the questions are:
Can we maintain the same warehouse number and do the customizing on it (deactivate Decentralized WMS and so on)? Or we must define a new one?
In both cases, (maintain the same warehouse number or define a new one) how can we transfer WM stock from decentralized to centralized?
Thanks
Michele

Merits and Demerits of Multiple company codes

Hi SAP Gurus,
Could you please let me know the Merits and Demerits of multiple company codes in ECC 6.0. Actually client asking for separate company codes for each production plant. Client having 20 plants (Client registered as one legal entity as per companies Act having 20 plants in different regions with in India) and wants to have separate company codes in SAP to have decentralized control of operations and period closing. Could you please let me know the merits and demerits of Multiple company codes with respect to Load on system, Extra activities/ load on man power on consolidation, complexities ect..
Thanks in Advance
Best Regards
Raj

Ray,
From the background explained by you, I feel that you should go for a single company code as they have one singel legal entity. The purpose of comapny code is to generate external reporting(mainly balance sheet & Pand L statement) as per the legal requirements.
As far as decentarlized control is concerned you can opt for configuring each plant as a separate profit center which will not only allow decentralized operations and accountability but also a flexibility from internal maangement point of view.
As far as configuration of multiple comapny codes is concerned, it will make the system too cumbersome and will have undesired complexity.
Hope this helps.
Rgds
Manish

ASCP Instance setup - DB LInk Creation in decentralized configuration

I came across this question on setting up the APS for decentralized configuration and really couldn't find why? The question was why do we need to create two DB links (One in Source for destination db and other one in destination for source db) and can we setup ASCP instance by creating only one DB Link, either at destination or at source?
Thanks
Madhavi

Hello,
The reason for this is that there is 2 way communication for the planning products.
On the planning instance the dblink is required when you run collections and release recommendations from the workbench (amongst other actions)
on the source, when you perform for instance an ATP inquiry, data is being read from the aps instance.
This is the design of ASCP. Both links are required.
regards
Geert

Difference between controlling budgetting and funds management

Hi All,
Can any one please explain me about the differece between controlling budgeting and funds management.
What are the additioanl features available in funds management when compared to budgetting in controllin
Thanks in Advance
Raka

Hi Raka,
FUNDS MANAGEMENT
The mySAP Public Sector solution plans and controls the flow
of revenues and expenditures, guides you through planning and
creating budgets, and uses active availability control to monitor
management appropriation. Funds management capabilities
simplify the design of budget plans using special planning techniques
and make it possible to differentiate provisional budget
plans. The solution supports centralized and decentralized
planning and budget execution of funds.
Controlling budgets is a headache for businesses of all sizes. Many smaller businesses start off
on the right foot by putting in place a good book-keeping system, but then fail to exercise
proper financial control and end up in trouble. The only way to make sure that you make a
profit is to control the budget efficiently. To do this, you need to estimate your sales income
reasonably accurately, estimate your costs precisely, and keep both under control. You also
need to charge the right price for your end product in your chosen market(s). It is important
systematically to collect all financial documents in a methodical way, and keep all your figures
up to date on a daily basis. This actionlist will look at some of the most common problems in
controlling a budget, and suggest ways to tackle them
Regards,
Srinivas Muthyala

Hi frnds urgent

hi
i am sirisha. i would like to ask one question reagrding open order.
 1. what is meant by open purchase orders
 2. what is meant by open Sales orders
 3. What is meant by BOM( Bill of Material)
with regds
Sirisha.

Hello,
Open purchase orders
Open Purchase Order = Open Goods Receipts ( Selection parameters WE101)
This two parameters determined what information is shown:
selection parameter
scope-of-list parameter
The configuation transaction code is OMEM
You can define additonal selection parameter for your users as well as untick those fields which you does not want it to be printed.
Your can have the Purchasing Documents by :-
ME2L - Vendor
ME2M - Material
ML93 - Service
ME2K - Account Assignment
ME2C - Material Group
ME2B - Requirement Tracking Number
ME2N - Purchase Order Number
ME2W - Supplying Plant
Open Sales order
Open Text solutions for Sales provide a comprehensive solution that virtually consolidates order information for central aggregation and management while providing for decentralized input and distributed visibility. Customer Order Management integrates with existing Enterprise Resource Planning (ERP) systems to consolidate order information from sales, marketing, credit, finance, tax, customer service and approval information for streamlined access and use.
BOM( Bill of Material)
Bill of materials ..it's kind of materials list.
Assume that u want to manufacture a computer.
computer contains lot of components..
so under computer this all component materials comes..
again among them if u take CPU part...it further drill down to some more materials...
This is called ..Bill of Materials...
In SAP this wud maintained in tables about this part materials info for a particular material.
u can check MAST table for some clarification.
Hope u r clear about this term
A bill of materials (BOM) describes the structure of an assembly. Each BOM object represents a part or subassembly
MAST Material to BOM Link (MM related)
Reward with points if its helpful :-)
Cheers,
Sachin

Decentralize warehouse management

Dear Friends,
This is the question related to warehouse management system.
My requirement is that we are going to set decentralize management. Presently we are having CWM in our present system. At another place there is local ERP , we want to replace it and need to go for decentralise WM there.
Then this decentralised WMS and my present WM willl communicate with each other.
Could you please let me know what will be it process ? Transaction cycles ? and its configuration?
Regrads,
Mahesh

Dear All ,
I got some information I am sharing with you and closing this ticket.
1) Process :
rocesses Between the SAP System as ERP System and as WM System
Purpose The variant for the SAP System as an enterprise resource planning (ERP) system and as a Warehouse Management (WM) system describes the link-up of an external warehouse management system to an SAP System. The stand-alone system that executes all warehouse management functions is an SAP System. Prerequisites Two systems are involved in this scenario. The first system is an ERP system that performs inventory management, purchasing and sales tasks and distributes existing master data and movement data to the Warehouse Management system (WMS). The second system is a WMS that performs warehouse management tasks such as putaway/picking and goods receipt/goods issue and is responsible for carrying out the physical material transfers. Process and Data Flow General inventory postings: If the decentralized scenario is used, inventory postings are not directly processed in Inventory Management (IM). If a goods movement is created in IM, the system generates inbound or outbound deliveries and distributes them to the WMS. In the WMS, the goods are put away or picked based on the existing delivery. As a result of the goods movement posting in the WMS delivery, the system sends the completion verification to the ERP system and then uses the delivery to post the actual goods receipt or goods issue in inventory management. Deliveries with a purchase order or a sales order as a source document are handled in the same way. Goods receipts based on purchase orders: You use the ERP system to create purchase orders and send them to the vendors. To give notification of the delivery that is due, the vendor returns a shipping notification that is recorded in the ERP system as an inbound delivery. The inbound delivery is distributed to the WMS using a Business Application Programming Interface (BAPI). In the WM system, the inbound delivery is a request to put away or pick goods. When the vendor physically delivers the goods, a transfer order is generated in the WMS which is used to place the goods into stock. After the transfer order is confirmed, goods receipt is posted for the inbound delivery. This clears the interim storage bin. As a result, the completion confirmation is sent to the ERP system and the goods receipt is processed in inventory management. An inbound delivery based on a purchase order can be created in different ways, depending on the confirmation control key in purchasing. If the vendor usually sends a shipping notification, the inbound delivery is created when the shipping notification is recorded in the system. In all other cases, you have the option of creating inbound deliveries automatically using collective processing. Process for goods receipts based on a purchase order: Creating the purchase order in the ERP system Generating the inbound delivery (automatically/manually) Distributing the inbound delivery from the ERP system to the WM system using BAPI method "InboundDelivery.SaveReplica" (this process is automatically executed in the background) Physically receiving the goods into the warehouse (WMS) Creating the transfer order Putting the goods away Confirming the transfer order Posting goods receipt for the inbound delivery (as a result, a completion verification is sent to the ERP system using BAPI method "InboundDelivery.ConfirmDecentral") Goods receipt for the inbound delivery is automatically posted in the ERP system (in inventory management) when the verification is recorded. Quality management in decentralized WMS using handling units (HUs) Quality management is also available in the goods receipt process in the decentralized warehouse. In this scenario, the quality management function is in the central system. If there are handling units in the inbound delivery for which an inspection lot has been created, the inspection lot number is copied into the decentralized WMS and stored in the quants there. The inspection lot does not exist in the decentralized system. You make the usage decision for the inspection lot in the central system, which triggers the system to create a posting change delivery and distribute it to the decentralized system. Then, the stock that belongs to this inspection lot is found in the warehouse and the corresponding posting change is made. From this point on, the procedure is the same as that of a posting change (see below). Other goods receipts: All other goods receipts are recorded in the ERP system. When the document is saved, the system creates an inbound delivery and sends it to the WM system using a BAPI. The inbound delivery is then processed in the WM system as described above. When the verification for the inbound delivery is sent to the ERP system, the goods receipt posting is automatically initiated in inventory management. Stock transfers: A stock transfer usually involves two storage locations (plants): the issuing storage location for picking and the receiving storage location for putaway. If the stock transfer is recorded in the ERP system as a two-step procedure and if one of the storage locations involved is a WMS-relevant storage location, the system creates a delivery for this posting and sends it to the WMS. Both storage locations involved are copied into the delivery to allow the actual posting to be executed after the verification is received from the WMS. One-step stock transfers using a WMS-relevant storage location are only possible if a storage location that is not WM-relevant is involved in the posting change. Process for stock transfers: Entering the goods movement in the system Automatically creating the delivery Distributing the delivery from the ERP system to the WM system using BAPI method "InboundDelivery.SaveReplica" (this process is automatically executed in the background) Physically receiving the goods into the warehouse or removing the goods from the warehouse (WMS). Creating the transfer order Putting away or picking the goods Confirming the transfer order Posting goods receipt for the inbound delivery (as a result, a completion verification is sent to the ERP system using BAPI method "InboundDelivery.ConfirmDecentral") or posting goods issue for the outbound delivery (as a result, a completion verification is sent to the ERP system using BAPI method "OutboundDelivery.ConfirmDecentral"). Goods receipt for the inbound delivery or goods issue for the outbound delivery is automatically posted in the ERP system (in inventory management) when the verification is recorded. When the goods receipt or goods issue is posted in the ERP system, the stock transfer is simultaneously posted in inventory management. Goods issues based on sales orders: The system uses sales orders to generate deliveries in the ERP system. The deliveries are then sent to the WMS. You use the WMS to create the transfer order, pick the goods and confirm the transfer order. When goods issue is posted, the picking quantities are passed on to the delivery of the ERP system. Process for goods issues based on deliveries: Creating the sales order Creating the outbound delivery Distributing the delivery to the WMS Creating the transfer order for outbound delivery Physically picking the goods in the warehouse Confirming the transfer order Printing the shipping documents, if appropriate Posting goods issue for the outbound delivery (as a result, a completion verification is sent to the ERP system using BAPI method "OutboundDelivery.ConfirmDecentral") Goods issue for the outbound delivery is automatically posted in the ERP system (in inventory management) when the completion confirmation is recorded. Posting changes You can also initiate transfer postings in the central system, in which case the stock change will be compared with the stock in the decentralized system and adjusted, if necessary. If you use inventory management to make posting changes in the central system, the system first generates a delivery. This delivery is technically a request for the decentralized system to make a transfer posting for the stock involved. The central system does not create material documents or make any changes in stock at this point. The delivery is transmitted to the decentralized system and, as of this point, can only be changed there. You can make settings in the decentralized system so that the system automatically creates a transfer order that corresponds to this delivery that does not require confirmation. You can also set the system to make the appropriate transfer posting in the WM stock automatically at the end of the process. The transfer posting in the decentralized system simultaneously verifies the appropriate quantities to the central system. When the central system receives this verification, it automatically makes the stock change and creates a material document. You can display the material document in the delivery’s document flow. Production supply If the decentralized warehouse is also responsible for production supply, the following two methods of material staging are available in the system: Production staging by switching storage locations Production stock is managed in a storage location that is located somewhere other than in the decentralized warehouse. In this case, the production storage location is not managed in the decentralized warehouse. If you switch the storage location in the central system, the system generates a delivery, for which you can then pick and post goods issue in the decentralized system. At this point, the stock that has been staged using this method can be used in a manufacturing order in the central system. Goods issue posting for a manufacturing order In this scenario, the raw materials are taken directly from the decentralized warehouse’s storage location and used in the manufacturing order. If goods issue is posted for the manufacturing order in the central system, the system creates a delivery that is sent to the decentralized system. The rest of the process is the same as regular goods issue processing. Note the following distinctions with regard to reservations: Delivery does not trigger request generation If the goods issue posting that generates the delivery refers to a reservation, the reservation number is copied into the delivery. In this case, the delivery does not check for availability and no requirements are generated, since that was already done in the manufacturing order. The reservation is canceled when the actual goods issue posting is made. Changes disappear after the delivery is distributed Keep in mind that if the reservation is changed in the meantime (if the production quantity has changed, for example), this change will not affect the delivery. Similarly, a change in the delivery will not result in a change in the reservation. The WM/PP interface, which you can use for production supply in an integrated system, is not supported for decentralized warehouse processing. This function is not available decentrally because the WM/PP interface is based on the assumption that WM and PP are running in the same system, which is not the case in a decentralized system. Goods receipt for a manufacturing order You can process goods receipts from manufacturing orders in the decentralized WM system. For goods receipt postings, the central system first creates an inbound delivery for the manufacturing order and distributes it to the decentralized system. In the decentralized system, the inbound delivery serves as a basis for putaway in WM. You can correct quantity differences here. Once you have confirmed the putaway transfer orders, goods receipt is posted in the decentralized system. The decentralized system then reports the quantity that was posted back to the central system. This verification automatically makes the actual goods receipt posting for the manufacturing order, along with the material document, in the central system.
2) Config we will get from Google also we will get standard idocs for ib and out bound.
Regards,
Mahesh

Bapi for Delivery Status

Hi Experts!
Can anyone tell me the BAPI to Display the Delivery Status
for a particuler sales order no or document no.
Thank U...

hi,
BAPI_DELIVERYFREE_PROXY_CREATE Proxy BAPI für Upload einer kostenlosen Nachlieferug SFA-Kontext: Anle
                                                                                LE_SHP_DB_DELIVERY_BUFFER      Object Buffer Delivery w/Database Access
BAPI_DELIVERY_GETLIST          BAPI for Reading Delivery Data
OIU_DELIVERY_NETWORK           Object Buffer Delivery w/Database Access
BAPI_DELIVERY_NETWORK_CHANGE   Delivery Network BAPI for Changes
BAPI_DELIVERY_NETWORK_CREATE   BAPI for creating a delivery network
BAPI_DELIVERY_NETWORK_READ     Display delivery network details
BAPI_INB_DELIVERY_CHANGE
BAPI_INB_DELIVERY_CONFIRM_DEC BAPI for Inbound Delivery Verification from a Decentralized System
BAPI_INB_DELIVERY_SAVEREPLICA BAPI Function Module for Replication of Inbound Deliveries
BAPI_OUTB_DELIVERY_CHANGE
BAPI_OUTB_DELIVERY_CONFIRM_DEC BAPI for Outbound Delivery Confirmation from a Decentralized System
BAPI_OUTB_DELIVERY_CREATENOREF Generates Delivery Without Reference
BAPI_OUTB_DELIVERY_CREATE_SLS Generates Delivery for Customer Order
BAPI_OUTB_DELIVERY_CREATE_STO Generates Delivery for Stock Transport Order
BAPI_OUTB_DELIVERY_SAVEREPLICA BAPI Function Module for Replication of Outbound Deliveries
BAPI_OUTB_DELIVERY_SPLIT_DEC   BAPI for Subsequent Outbound-Delivery Split from a Decentralized Syste
and for "Shipment
BAPI_SHIPMENT_CHANGE           Change Shipment
BAPI_SHIPMENT_COST_ESTIMATE    Calculate Shipment Costs of Different Forwarding Agents for Shipment
BAPI_SHIPMENT_CREATE           Create Shipment

How to use BAPI_INB_DELIVERY_CONFIRM_DEC do batch split

Hi, everyone:
I want to do batch split in inbound or outbound delivery by function.
I found BAPI_INB_DELIVERY_CONFIRM_DEC, but our system is not a Decentralized System and I wandered in so many parameters.
How to use this fuction?
Thanks.

Hi Junwen,
Did you call the BAPI_TRANSACTION_COMMIT afterwards?
Before this the data is not saved. After that it is saved.
Regards,
Rob.

STO with Delivery

Hello, In STO from plant to plant
i have created one sto with three line items STO is created but when i
create a Delivery the delivery is created for only two line items , it will not create delivery for(VL02n) third line item why what is the reason
i have checked the stock of material in MMBE, and in MD04 also stock is more no problem then what is the reason................
regards
sapman

In a company, goods movements do not only occur in the form of goods receipts and goods issues. Depending on the organization of the company (for example, decentralized storage) and its sales policy, internal stock transfers might also be necessary.
The stock transfer with delivery is a plant to plant scenario. You are posting a goods issue in plant BP02 and a goods receipt in plant BP01.
This type of stock transfer can only be carried out from unrestricted-use stock of the issuing plant to unrestricted-use stock of the receiving plant.
You post the placement into storage at the receiving plant in a second step. Only then is the event completed and the transferred quantity part of unrestricted-use stock.
Function List
The following functions are provided to support the J51 building block:
Creating a Planned Independent Requirement
Creating a stock transport order in plant BP01
Generating a delivery in plant BP02
Picking of the material and posting the goods issue in the delivering plant
Posting the goods receipt in the receiving plant
Key Points
The quantity posted from stock is first of all managed as stock in transit of the receiving plant. Only once the goods receipt has been posted is the quantity posted to the unrestricted-use stock of the receiving plant. This enables the quantity "on the road" to be monitored.
The transfer posting is valuated at the valuation price of the material in the issuing plant.
Delivery costs can be entered in the stock transport order.
http://help.sap.com/bp_bblibrary/500/html/J51_IntProcSTwD_EN_IN.htm
Regards,
Rajesh Banka
reward points if helpful.

DIT Design -- Handling users in overlapping & changing groups/institutions

Hi Folks-
[My Apologies if there are duplicates, the forum doesn't show any sign of accepting this]
I've been working on a DIT Design to solve a set of business requirements which conflicts with most traditional approaches. I've got some (overly) complicated ideas, but I'm wondering if anyone has encountered a similar situation, and if so did you find a good solution.
Key Requirements:
(1) We have a collection of users from various institutions and groups within them.
(2) (THE MAIN WRINKLE) A certain amount of overlap and movement between institutions is expected (group overlap will be common). A user who is in overlapping institutions or moves between them MUST use a single, shared identity and SHOULD maintain a stable identity (i.e. no DN changes).
(3) Much of the user administration should be decentralized and done at the group level (within each specific institution). An administor of GroupA in Foo Institution should only be able to administer the users in GroupA at Foo, but must be able to control membership within GroupA. Special precautions are permitted to keep a Group-A/Foo administrator from hijacking an arbitrary user by adding the target user to Group-A/Foo.
(4) The number of institutions is expected to be start around 40-50, and could scale to the thousands. The number of people will probably be around 5-20 times the number of institutions. The design should accomodate that scale.
Additional Notes:
(A) I don't see any alternative to keeping any organizational information out of the users' DN's, essentially flattening the users out (I've currently got them all in one container).
(B) I can obviously setup a hierarchy of roles/groups in institutional containers to handle membership and group administrator lists. All Directory Server administration will be done by a small central team and everything can be in containers under a common root suffix.
(C) We currently have the necessary skillsets to develop scripts and programs as needed. But 2 different application families (incompatible foundations -- Java vs. Cobol+Perl) are already scheduled for deployment against this (hopefully more will follow). This means it's not very practical to use one "LDAP Superuser" id and rely on the application to enforce security policies. We really want to put as much of the security into the Directory as possible (calling for individual LDAP admins w/ the appropriate rights), but we can supplement it where we need to.
(D) It looks like I'll have to rely heavily on filters based on the values of particular attributes of each user (whether in ACI's, Filtered Roles, or the like). Unfortunately, I don't see many ways that I can actually build those filters to be dependent on attributes/values of different entries. But I'm still working on that.
(E) Because of the number of institutions (and probable continous growth), writing a master upper-level ACL which has each institution & group explicitly coded is probably unwise due to size and stability. If I have to I could have a helper program custom-code each user's ACL differently and change it as needed. But that doesn't seem like a good solution.
Right now the designs I'm tossing around are calling for combinations of (all/most of) Roles (Filtered & Nested), Groups, CoS Template & Password Policies (yeah, we need those too), Macro ACI's, and a small amount of helper scripts and programs. We're running 5.2 but can probably upgrade to 6.0 if I can cite a good enough reason.
My current design is pretty ugly and complicated but probably attainable. If people are interested enough I'll post a cleansed summary once it's working.
Has anyone tackled anything like this before, and does anyone see any cleaner approach I've missed?
Thanks,
-Scott-

Hi-
We're basically putting all the users in one big container making a flat space.
We then create lots of roles, each of which corresponds to a particular combination of institution, application, and access type/level (the user is implicit as it contains the nsRole). If a user has multiple types of access to an application for a given institution then they will be in multiple corresponding roles.
We have the roles grouped together in a subtree which is divided by institution (and could be further subdivided by application within each institution or placed in the reverse order). But because of the scoping restrictions on nsRole's only a nsNestedRoleDefinition can be placed at this location (using nsRoleScopeDN), the Managed and Filter "working roles" must be in a branch of the tree above all things which will be contained within them (we put it at the top of that naming suffix).
According to the docs, queries will ignore a ldapSubEntry (which all of the nsRoleDefinition's are) unless specifically requested, so the fact that there are hundreds or thousands of roles defined at the top shouldn't matter. However, all of the GUI's I've tried displayed all the roles.
Currently the application code parses the DN of the role names from the user's nsRole entry, NOT the nsRoleDN entry. There end up being a lot of intermediate roles which get ignored. It uses this to determine the access type(s) to be granted. This is really convenient since one query for the user gets everything. However it builds dependencies into the DN format which arguably probably shouldn't be depended on. I've considered defining custom schema attributes which would contain the application/institution/access tuples (which could also be helpful for building nsFilteredRoleDefinition's), but that represents another round of queries and more substantial code changes for the pilot application.
Once in place, the roles can easily be nested and combined in various ways (such as "roll-up" roles containing all users of an application). They can also be used for password policies, CoS templates, and building ACI's. The last should be very helpful in enabling decentralized administration, but that's going to be pretty dependent on your security policy.
An issue with decentralized administration and Managed Roles is that normally anyone who can modify a user's nsRoleDN attribute can place any role in there, which isn't desirable in this environment. I haven't moved forward with the ACI work yet, but it appears that the "targattrfilters" ACI keyword may allow this problem to be solved (possibly in conjunction with Macro ACI's). Using some custom attributes with filtered roles might make this easier.
So, we could have something like this very incomplete LDIF (not checked for errors), only the really important attributes are shown. Also similar entities with the same naming patterns have been omitted.
dn: cn=appusers,ou=webmail,ou=inst01,ou=institutions,o=naming-suffix
objectClass: nsNestedRoleDefinition
nsRoleDN: cn=managed-webmail-inst01-appusers,o=naming-suffix
nsRoleDN: cn=filtered-webmail-inst01-appusers,o=naming-suffix
nsRoleScopeDN: o=naming-suffix
dn: cn=managed-webmail-inst01-appusers,o=naming-suffix
objectClass: nsManagedRoleDefinition
dn: cn=filtered-webmail-inst01-appusers,o=naming-suffix
objectClass: nsFilteredRoleDefinition
nsRoleFilter: (customAppInstAccess=webmail:inst01:user)
dn: uid=jsmith,ou=users,o=naming-suffix
nsRoleDN: cn=managed-webmail-inst01-appusers,o=naming-suffix
nsRoleDN: cn=managed-webmail-inst01-appadmins,o=naming-suffix
dn: uid=jappleseed,ou=users,o=naming-suffix
nsRoleDN: cn=managed-webmail-inst01-appusers,o=naming-suffix
customAppInstAccess: blogger:inst03:user
customAppInstAccess: webmail:inst03:userSo jsmith's nsRole attribute would contain the following values (the ones above the blank line are the main entries, the others are intermediate role to be ignored):
cn=appusers,ou=webmail,ou=inst01,ou=institutions,o=naming-suffix
cn=appadmins,ou=webmail,ou=inst01,ou=institutions,o=naming-suffix
cn=managed-webmail-inst01-appusers,o=naming-suffix
cn=managed-webmail-inst01-appadmins,o=naming-suffixAnd jappleseed's nsRole attribute would contain the following values (the ones above the blank line are the main entries, the others are intermediate role to be ignored):
cn=appusers,ou=webmail,ou=inst01,ou=institutions,o=naming-suffix
cn=appusers,ou=blogger,ou=inst03,ou=institutions,o=naming-suffix
cn=appusers,ou=webmail,ou=inst03,ou=institutions,o=naming-suffix
cn=managed-webmail-inst01-appusers,o=naming-suffix
cn=filtered-blogger-inst03-appusers,o=naming-suffix
cn=filtered-webmail-inst03-appusers,o=naming-suffixIf that doesn't make sense, then you can email me details of what you're trying to do at <[email protected]>, but it may take some time before I can respond.
-Scott-

Movement type in delivery

hi,
We all know that Movement Type in Dlivery document is through Sceduline category of Sales order.
but how about the Outbound Delivery movement type 643 comes in for Stock transport order. We have UB PO created, which follows outbound delivery created using VL10G and mvt type come is 643. Where does this come from.

Dear Mahesh,
In IMG under
Materials Management -> Inventory Management and Physical Inventory -> Movement Types -> Copy, Change Movement Types
Stock Transport Order:
http://help.sap.com/saphelp_47x200/helpdata/en/4d/2b911d43ad11d189410000e829fbbd/content.htm
http://help.sap.com/saphelp_47x200/helpdata/en/4d/2b917843ad11d189410000e829fbbd/content.htm
http://help.sap.com/saphelp_47x200/helpdata/en/4d/2b918543ad11d189410000e829fbbd/content.htm
Building Block on Cross Company Sales order processing:
http://help.sap.com/bp_bblibrary/500/html/J62_CCSOP_EN_DE.htm
A customer places an order which cannot be filled by the vendor. The vendor therefore sends the goods to the customer from a plant belonging to another company code.
Sales order is created by sales organization BP01 in company code BP01. The goods are not available in a plant belonging company code BP01 and must be shipped from a plant belonging to a different company code, BP0X.
Customer invoice is issued by the sales organization BP01 in company code BP01, while the distribution plant belonging to company code BP0X uses inter-company billing with the sales organization BP01.
Delivering plant belongs to a different company code
Direct delivery from delivering plant to customer
Customer invoice and inter-company billing document
Internal transfer prices
Stock Transfer Order:
Whenever you need to transfer the materials from one plant to another plant belonging to one company or belonging to two company code stock transfer order is raised by the delivering company.
Transfer of goods from one location to another location,it may be between plants within the same company code or in different company code's plants.
within the company code, bet plants, receiving plant will raise the STO in Supplying/issuing plant-ME21n,
Supplying plant will deliver the goods to receiving plants , then we need to pick n post the Goods Issue-VL02n, nw when we can observe that the STO qty will be added into receiving plant and reduced in Delievering plant.
To do this, we need do prior customizatin in SPRO-IMG,-material should be created in both plants( receiving & Supplying)
-maintaing the stock only in supplying plant
-create a dummy customer in supplying plant's sales area(if u have one sales area, create in tat comp code n sales area)
-Assign this customer number to receiving plant's details along with the sales area,
-Assign the STO doc type(UB) to Supplying plant, along with checking rule
-Assign the Del type (NL/NLCC) to Supplying n receiving plant.
You create a STO from MM route i.e., ME21N and then enter the details of the supplying,receiving plant and the materials.Once you complete the STO,then it goes for a delivery followed by an intercompany invoice.
Remember that the Material should be there in BOTH supplying and receving plant.
Internal Procurement (Stock Transfer With Delivery):
In a company, goods movements do not only occur in the form of goods receipts and goods issues. Depending on the organization of the company (for example, decentralized storage) and its sales policy, internal stock transfers might also be necessary.
The stock transfer with delivery is a plant to plant scenario. You are posting a goods issue in plant BP02 and a goods receipt in plant BP01.
This type of stock transfer can only be carried out from unrestricted-use stock of the issuing plant to unrestricted-use stock of the receiving plant.
You post the placement into storage at the receiving plant in a second step. Only then is the event completed and the transferred quantity part of unrestricted-use stock.
Functions:
Creating a Planned Independent Requirement
Creating a stock transport order in plant BP01
Generating a delivery in plant BP02
Picking of the material and posting the goods issue in the delivering plant
Posting the goods receipt in the receiving plant
Note: The quantity posted from stock is first of all managed as stock in transit of the receiving plant. Only once the goods receipt has been posted is the quantity posted to the unrestricted-use stock of the receiving plant. This enables the quantity "on the road" to be monitored.
The transfer posting is valuated at the valuation price of the material in the issuing plant.
Delivery costs can be entered in the stock transport order.
Internal Procurement (Stock Transfer without Delivery):
The cross-plant, internal procurement of materials can be carried out within one company code (intercompany) or by using several company codes (cross company). This process can be dealt with using standard functions such as material requirements planning, purchase requisition, stock transport order, transportation planning and the handling of internal deliveries.
The following functions are provided to support the Internal Stock Transfer without Delivery:
Create Stock Transport Order
Post goods issue for stock transport order
Post goods receipt for stock transport order
Note: Quantity "on the road" can be monitored
Delivery costs can be entered in the stock transport order
Internal Procurement (Cross-Company Stock Transfer):
You post a stock transfer from company code to company code the same way as you post a stock transfer from plant to plant, except that both plants belong to different company codes.
During the stock transfer, two accounting documents are created in addition to the material document:
-An accounting document for the removal from storage at the issuing company code
-An accounting document for the placement into storage at the receiving company code
The stock posting is offset against a company code clearing account.
To display the value of the cross-company-code stock in transit with a report, choose Environment à Stock à Stock in transit Cc.
The following functions are provided to support the cross company stock transfer:
Create sales order to customer
Run single-level MRP
Creating a purchase order
Creating delivery
Picking and post goods issue
Posting goods receipt
Create inter-company billing document
Invoice receipt
Create delivery, picking and post goods issue to customer
Billing
Notes: The issuing plant enters a delivery for the stock transport order and a billing document. This is an inter-company billing document (billing type YBIV). Pricing takes place as normal.
When the goods arrive, the receiving plant posts a goods receipt for the purchase order. The unrestricted-use stock increases and an accounting document is created.
The invoice is checked with reference to the purchase order.
Stock transport order processing in receiving plant
Delivery processing in supplying plant Picking batch determination in delivery Goods issue processing in the supplying plant Billing processing in supplying plant
Goods receipt processing in receiving plant Invoice verification processing in receiving plant Purchase order monitor processing in receiving plant
Regards,
Naveen.

Decentralized WM and Hu's

Similar Messages

Maybe you are looking for