Centralized/Decentralized Purchasing
Hi all,
What is Diff between centralized and de-centralized purchasing in SRM???How is it defined at the Org structure level??
HI
Centralized Purchasing:
Where the purchasing activity is carried out by a central purchasing organization for all of your subsidiaries. In the context of SRM, centralized purchasing can be as below that each of your individual org captures the requirement in purchase requisition and sends it to SRM system (which is handled by centralized purchasing orgaization) through Plan driven procurement or CPPR scenario. Once the requirement is sent to SRM, the central purchasing org either creates PO or contract in the SRM system.
Decentralized purchasing:
Here the purchasing happens locally in each org. The centrally negotiated contract is distributed to all the backend systems. Now, the local purchasing org avails the distributed contract in the backend system to meet his requirement.
Thanks and regards,
Ranjan
Similar Messages
-
Central Contract/Purchasing Contract
Hi All,
What is the difference between Central contract and Purchasing contract in SRM 7.0
Also , can we dispaly the central contract in ECC using the transaction code Me33k .
Thanks,
AshishHi,
Purhasing contracts are contracts created in SRM only and never accesed in ERP system. This contract can be used as source of supply in SRM only.
Central contracts are the contracts created in SRM and then distributed to ERP system and YES you can access this contract with me33k. Here the SRM contract and ERP distributed contracts will have the same document number. This contract can be used as source of supply in both ERP and SRM system.
Please note that SRM central contract is the main document where you can make changes and the same contract is displayed in ERP with minimal data.
Regards
Sam -
Number Range for Purchasing Groups
Dear All,
I need to assign different number range for purchase order for different purchasing groups of same dosument type. In fact we want to distinguish purchase document depending on number range for different purchasing groups.
Regards,
VikasHi,
Document type concept is used when your procurement process is differ from standard procurement processes , that time you can go for u201CNew document typeu201D. For example: Standard procurement document type is u201CNBu201D when you have procurement processes like sub-contracting and formal order, that time you used different document type other then u201CStandard document typeu201D with new respective number ranges.
Also you have a way to keep different document type with number ranges if two company code there & your business required to have PO document type with number range W.R.T. Company Code then can use User Exit M06B0003 ,MM06E003 & M06B0004 where you have option to have PO number range based on Company Code.
But as you required different number range for purchase order for different purchasing groups, You can use centralized & decentralized purchasing groups & can have centralized & decentralized PO document types and can control all authorization in basis side.
Regards,
Biju K -
Dear Friends
I am confuse with the below things
1. Purchase organization
2. Std purchase organization
3. Reference purchase organization
4. Centralised purchase organization
5. Decentralized purchase organization
my understanding is : Reference purchase organization would not procure, std purchase org handle consignment,stock transfer,pipeline. If so what is the role of purchase orgaziation not std purchase organization.
Centralized purchase organization - procurement process for one particular plant where as why we have to assign the purchase organization to plant and company code, otherwords, for company code specific pur.org we assign for both plant and company code.
Pls advise me.
Thanks
Rajakumar.KHi Raja
Try to imagine as per below..
Std PORG:If several purchasing organizations procure for a certain plant, you can designate one of them as the standard purchasing organization for the transactions pipeline, procurement, consignment, and stock transfer. In the source determination process for stock transfers and consignment, the system then automatically pulls this standard purchasing organization. In the case of goods issues of consignmentand pipeline materials, the purchasing info records of the standard purchasing organization are read.
Reference PORG: You can use a reference purchasing organization to facilitate cross-purchasing-organization procurement transactions. It is possible for other purchasing organizations to use the conditions of a reference purchasing organization for price determination purposes. Similarly,it is also possible for several purchasing organizations to be allowed access to the contracts of a certain reference purchasing organization.
Centralized PORG: A Centralized PORG purchases for all the plants across all the company codes, therefore as a rule the central purchasing dept. of a corporate group is not assigned to any company code.
Decentralized PORG: This can be as per the requirements e.g suppose you have two company codes assigned to one company. then u can view decentrailzed PORG as two PORGs responsbile for these two comapny codes. (but for all the plants under each of the two company codes)
Hope this would help clear somewhat.
Regards -
REPOS indicator in Purchase Order
Dear All,
Do you know if it is possible to set up the PO type, that the indicator REPOS (Invoice Receipt) will be always not flagged?? (no invoice will be expected in this PO type)
If this kind of setting is possible, where can I do it??
Thanks in advance,
Sylwia
Edited by: S. KOWALSKA on Oct 1, 2008 1:50 PMblock the vendor centrally from Purchasing --> master data --> Vendor --> centrally
By this no IR will be generated for the PO...
Regards
Priyanka.P -
What is the difference between Reference Purchasing organisation and Central Purchasing organisation.
Vishal
See these examples
<b>Reference Purchasing Organisation</b>
A purchasing organization whose conditions or contracts other purchasing organizations linked to it may access and use.
A reference purchasing organization can make especially favorable conditions or contracts available to other purchasing organizations.
<b>Example</b>
http://help.sap.com/saphelp_47x200/helpdata/en/0b/ecb237e29bc368e10000009b38f8cf/frameset.htm
<b>Central Purchasing Organisation</b>
Centralized/Distributed Purchasing
You can organize your purchasing function in the following ways:
Centralized purchasing, with just one purchasing organization
Distributed purchasing, with a number of different purchasing organizations each responsible for different plants
You could also look this configuration on How to maintain Purchase Organisation
Maintain purchasing organization
In this step, you set up your purchasing organizations.
From the Materials Management and Purchasing view, the purchasing organization is responsible for all purchasing activities (including the processing of requests for quotations and purchase orders, for example).
The purchasing organization is integrated within the organizational structure as follows:
A purchasing organization can be assigned to several company codes.
(= Corporate-group-wide purchasing).
A purchasing organization can be assigned to one company code.
(= Company-specific purchasing).
A purchasing organization can also exist without being assigned to a company code.
Since each plant must be assigned to a company code, the latter can be determined via the plant at the time of each procurement transaction even if the procuring purchasing organization has not been assigned to a company code.
A purchasing organization must be assigned to one or more plants.
(= Plant-specific purchasing).
A purchasing organization can be linked to one or more other purchasing organizations.
(= reference purchasing organization)
For more on this topic, refer to Assign Purchasing Organization to Reference Purchasing Organization.
A purchasing organization can be divided into several purchasing groups that are responsible for different operational areas.
Each purchasing organization has its own info records and conditions for pricing.
Each purchasing organization has its own vendor master data.
Each purchasing organization evaluates its own vendors using MM Vendor Evaluation.
Authorizations for processing purchasing transactions can be assigned to each purchasing organization.
All items of an external purchasing document, that is, request for quotation, purchase order, contract, or scheduling agreement, belong to a purchasing organization.
The purchasing organization is the highest level of aggregation (after the organizational unit "client") for purchasing statistics.
The purchasing organization serves as the selection criterion for lists of all purchasing documents.
Possible organizational forms
You can organize your purchasing function in the following ways:
Corporate-group-wide purchasing
Company-specific purchasing
Plant-specific purchasing
All of these forms can co-exist within a single client.
Corporate-group-wide purchasing:
A purchasing organization is responsible for the purchasing activities of different company codes.
In this case, you do not assign a company code to the purchasing organization, but specify the company code concerned for each individual purchasing transaction. You assign plants from different company codes to the purchasing organization.
Company-specific purchasing:
A purchasing organization is responsible for the purchasing activities of just one company code.
In this case, you assign a company code to the purchasing organization. The purchasing organization may procure only for this company code. You assign only plants of the company code concerned to the purchasing organization.
Plant-specific purchasing:
A purchasing organization is responsible for the purchasing activities of one plant.
In this case, you assign the plant and the company code of the plant to the purchasing organization. The purchasing organization may procure for this plant only.
Note
If you wish to work with a mixture of the above organizational forms, the reference purchasing organization is of significance to you.
It is possible to allow one purchasing organization to access the contracts and conditions of another - a so-called reference purchasing organization. This makes it possible for advantageous terms negotiated by one purchasing organization to also be used by other purchasing organizations.
Recommendation
Purchasing organization 0001 is already preset in all dependent tables.
SAP recommends that you retain this number if you require only one purchasing organization.
You will then have to customize only a few tables.
Hope this helps
Thnaks
Sat -
Hi,
What could be the use of defining two or more z-document types for standard purchase orders. What are the factors influenced by document types.
Thanks and regards
AparnaHi,
When purchasing process is different then standard one, you can use different document type concept to differentiate the different process of procurement. Example standard procurement process different from Stock Transport Order process, sub-contracting process, so here you can use different document type.
Also you can have different document type may ZNB for purchase order WRT contract. Also you can drill down Contract with Purchase Order to ZNB (centralized purchase order WRT contract) and YNB (Decentralized purchase order WRT contract)
You can have different number range for a process & you have to define a different document type. The other standard document type are:
NB Standard Purchase Order
UB Stock Transport Order
FO Frame Work Order
Regards,
Biju K -
Dear friends,
I have such a requirement. We are implementing PO workflow. A PO is created with centralized and decentralized purchasing groups. If itu2019s created from a plant, it has to be approved by plant manager and purchasing manager at headquarters. My problem is we have 2 purchasing manager at headquarters that use same purchasing organization, purchasing group, company code, purchasing document type and etc. Is there any way that once PO is created from plant, the creator has to choose whether PO should go for approval to purchasing manager 1 or 2. I would like to hearing from you.
Regards
MelihYou have to create multiple releases with same specs like Release A and Release B. if you release A it will go to Manager 1 and for release B it will go to Manager 2. if any of one release get approval 2nd release will not required to be send.
Also you can assign particular user in Organizational Unit with the Manager.
If it helps, kindly give points.
Regards,
RM -
Need Analysis Questions for Procurement
Hi Experts,
Where could I find a set of need analysis questions to ask a potential client about their procurement process?
I am currently running my first need analysis workshop, and would like to know what kind of questions to ask the business so I can find out more about their business processess with regard to procurement.>
Lindsay Gossmann wrote:
> Hi Experts,
>
> Where could I find a set of need analysis questions to ask a potential client about their procurement process?
>
> I am currently running my first need analysis workshop, and would like to know what kind of questions to ask the business so I can find out more about their business processess with regard to procurement.
In general, the analysis should cover the following:
- Types of procurement departments, since there might be different departments for different kinds of purchases - perhaps different lines of business altogether.
- Process of procurement of each
- Centralized / decentralized processing
- Treatment of taxes / duties
- Inventory valuation procedures
- Quality checks during procurement
- Long term contracts / agreements
- Treatment of low value items (with or without purchase order)
- Approval process (release procedure)
- Stock transfer process across plants
- Subcontracting / consignment / pipeline requirements
- Process for vendor returns
- Scrap generation / storage
- Physical inventory process / frequency /writeoffs
- Treatment of freight and other charges
- Imports, if a different process is followed.
- Service procurement process
- Any special process associated with the company or industry.
Hope this covers most of the business processes related to procurement
Regards,
Aroop -
Check Credit and Stock on Sale Order
Hi All
Could you please tell me how to check Credit and Stock on Sale Order.
Thank and Best Regard
ThangHow To Do Configuration For Credit Management
Credit and risk management takes place in the credit control area. According to your corporate requirements, you can implement credit management that is centralized, decentralized, or somewhere in between.
An organizational unit that represents the area where customer credit is awarded and monitored. This organizational unit can either be a single or several company codes, if credit control is performed across several company codes. One credit control area contains credit control information for each customer.
For example, if your credit management is centralized, you can define one credit control area for all of your company codes.
If, on the other hand, your credit policy requires decentralized credit management, you can define credit control areas for each company code or each group of company codes.
Credit limits and credit exposure are managed at both credit control area and customer level. You set up credit control areas and other data related to credit management in Customizing for Financial Accounting. The implementation guide is under Enterprise Structure -> Definition or Assignment -> Financial Accounting and then Maintain credit control area. You assign customers to specific credit control areas and specify the appropriate credit limits in the customer master record.
Settings for determining the credit control area of a document. The settings of items 1 - 4 are taken into account according to their priority. The credit control area found is stored in field VBAK-KKBER.
1. Transaction OB38
Check which credit control area is assigned to the company code.
Company code:
Credit control area:
2. Transaction OVFL
Check which credit control area is assigned to the sales area.
Sales area:
Credit control area:
3. Transaction XD02 or VD02
Check which credit control area is assigned to the payer.
Payer:
Credit control area:
4. Transaction SE37
Is user exit EXIT_SAPV45K_001 being used?
5. Transaction OBZK
For the settings under items 2 - 4, field "All company codes" must be marked in Transaction
OB45, or the credit control area must be entered under the relevant company code in table
T001CM of the credit control areas allowed.
Company code:
Credit control areas allowed:
6. Settings for the credit checks
7. Transaction OVAK
Which settings do exist for the sales document type used?
Sales document:
Check credit:
Credit group:
8. Transaction OVAD
Which settings do exist for the delivery type used?
Delivery type:
Credit group for delivery:
Credit group for goods issue:
9. Transaction OB01
Credit management/Change risk category
Definition of the risk category for each credit control area. This risk category can be
assigned to a credit account by using Transaction FD32.
10. Transaction OVA8
Here, the individual credit checks for key fields
o credit control area
o risk category
o credit group are set. Take these key fields from the above settings and go to the detail
screen. In particular, check whether fields "Reaction" and "Status/block" are set
correctly. To carry out follow-up actions in case of a credit block, the credit check
status must be set (field "Status/block").
11. Transaction FD32
Credit master data for the payer of the relevant document.
Credit account:
Credit limit:
Risk category:
Currency:
12. Settings for updating the credit values Update of the credit values is required for the limit
check (static or dynamic credit limit check).
13. Transaction OVA7
Update of the credit value is active for the corresponding item type if the check box is marked. This field corresponds to
field "Active receivable" in Transaction VOV7.
Item type:
Active receivable:
14. Transaction V/08, Pricing
In the pricing procedure used for pricing, subtotal "A" must be entered in a line for
determining the credit value (mark the pricing procedure and doubleclick on "Control").
Usually, the net value plus taxes is used. This way the system is determined to use this
subtotal for credit pricing. The credit price is stored in field VBAP-CMPRE and used for
update and credit check.
You can find the used pricing procedure of the order under "Item -> Condition -> Analysis".
Pricing procedure:
Line with subtotal = 'A':
15. Transaction OB45
Which update group (field "Update") do you use in the relevant credit control area? The
default setting is "12". If you use another update group, check whether this is fine with
you. If you open an OSS message, please tell us the alternative update group.
Credit control area:
Update:
16. Transaction OMO1
Which kind of update did you choose for structure S066?
In any case, "Synchronous update (1)" has to be chosen as the kind of update.
All other settings will lead to errors
Regards
Raja
Edited by: ramanathan raja on Jul 25, 2008 4:37 PM -
Multiple contract creation in ECC from a single GOA
Hi Experts,
I am working on a solution regarding to GOA in SRM - Contract in ECC creation and i am wondering about the following scenario:
Create 1 GOA in SRM 5.0 for a central/global purchasing organization and when the appropriate BADI going to transfer it into ECC, it creates contracts for all company codes.
At my current client they use GOA but until now they created 1 GOA for a specific p.org and the BADI transferred (and created) contract in ECC for the specific company code (they donu2019t have kind of central/global purch organization unit in ppoma). In the future they would like to create GOAs which are usable for all companies, but instead of creating (and changing) them manually (N GOA in SRM for N contract in ECC) they want to have an automatism.
Does any of you have any experience on this? That would be really good if you can share with me some high level overview about concept.
Thanks in advance for your help!
Best Regards,
AttilaHi,
Let me correct if i am right:
- Central Contract -> new concept of SRM 7.0. 1 contract which is visible and usable from ECC and SRM as well. (not available in SRM 5.0 - agree)
- GOA -> it exist in SRM 5.0 for sure! (we are currenlty using it for ECC procurement).
The solution what you are mentioned is good...but as you said only for SRM 70...we are in SRM 5.0 and we need solution for here. Do you have any idea?
Currently i am thinking about a new solution based on "standard" functionalities: if a GOA need to be created for mulitple company, it has to be populated in Header distribution (all company will have the same contract header). It item detail all the required information need to be poupulate in SRM (i.e.: item 1 for p.org1/comp.cod1; item 2 for p.org2/comp.cod2).
When this is done, the BADI need to check the informatoin in SRM GOA and create contract according to that -> in this case 1GOA is created, but the 2 items for totally different p.org/comp.code, the BADI needs to create 2 different contract in ECC (i would like to avoid using reference purchasing organization in ECC!
Thanks in advance!
Best Regards,
Attila -
Hello,
i am having big confusion about the mandatory fields of fico tables, i asked the question regarding the same in expert somebody told me that mandatory fields are already clikmark in the filed of key/intial there i am having doubt that ok some fileds are already cliked in the field and rest of the fields are uncliked i can understood that the cliked fields are already in the master table and rest of the user have to enter that field then how to know the which fields are mandatory i mean uncliked fields i.e. key/initial.
also sending the screenshort for one table there the key/intial fields are cliked in top of the two coloums i can understood that are already loaded in the master table again user not necessary to enter that, i want to know rest of the fileds which are mandatory that i want to know, please help me soon and oblige.
TABLE: LFA1 (Vendor Master (General Section)
FIELD Key Initial DATAELEMENT DTYPE LENGTH
MANDT √ √ MANDT CLNT 3 Client
LIFNR √ √ LIFNR CHAR 10 Account Number of Vendor or Creditor
LAND1 LAND1_GP CHAR 3 Country Key
NAME1 NAME1_GP CHAR 35 Name 1
NAME2 NAME2_GP CHAR 35 Name 2
NAME3 NAME3_GP CHAR 35 Name 3
NAME4 NAME4_GP CHAR 35 Name 4
ORT01 ORT01_GP CHAR 35 City
ORT02 ORT02_GP CHAR 35 District
PFACH PFACH CHAR 10 PO Box
PSTL2 PSTL2 CHAR 10 P.O. Box Postal Code
PSTLZ PSTLZ CHAR 10 Postal Code
REGIO REGIO CHAR 3 Region (State, Province, County)
SORTL SORTL CHAR 10 Sort field
STRAS STRAS_GP CHAR 35 House number and street
ADRNR ADRNR CHAR 10 Address
MCOD1 MCDK1 CHAR 25 Search term for matchcode search
MCOD2 MCDK2 CHAR 25 Search term for matchcode search
MCOD3 MCDK3 CHAR 25 Search term for matchcode search
.INCLUDE SI_LFA1 STRU 0 Vendor Master (General Section)
ANRED ANRED CHAR 15 Title
BAHNS BAHNS CHAR 25 Train station
BBBNR BBBNR NUMC 7 International location number (part 1)
BBSNR BBSNR NUMC 5 International location number (Part 2)
BEGRU BEGRU CHAR 4 Authorization Group
BRSCH BRSCH CHAR 4 Industry key
BUBKZ BUBKZ NUMC 1 Check digit for the international location number
DATLT DATLT CHAR 14 Data communication line no.
DTAMS DTAMS CHAR 1 Report key for data medium exchange
DTAWS DTAWS CHAR 2 Instruction key for data medium exchange
ERDAT ERDAT_RF DATS 8 Date on which the Record Was Created
ERNAM ERNAM_RF CHAR 12 Name of Person who Created the Object
ESRNR ESRNR CHAR 11 POR subscriber number
KONZS KONZS CHAR 10 Group key
KTOKK KTOKK CHAR 4 Vendor account group
KUNNR KUNNR CHAR 10 Customer Number 1
LNRZA LNRZA CHAR 10 Account Number of the Alternative Payee
LOEVM LOEVM_X CHAR 1 Central Deletion Flag for Master Record
SPERR SPERB_X CHAR 1 Central posting block
SPERM SPERM_X CHAR 1 Centrally imposed purchasing block
SPRAS SPRAS LANG 1 Language Key
STCD1 STCD1 CHAR 16 Tax Number 1
STCD2 STCD2 CHAR 11 Tax Number 2
STKZA STKZA CHAR 1 Indicator: Business Partner Subject to Equalization Tax?
STKZU STKZU CHAR 1 Liable for VAT
TELBX TELBX CHAR 15 Telebox number
TELF1 TELF1 CHAR 16 First telephone number
TELF2 TELF2 CHAR 16 Second telephone number
TELFX TELFX CHAR 31 Fax Number
TELTX TELTX CHAR 30 Teletex number
TELX1 TELX1 CHAR 30 Telex number
XCPDK XCPDK CHAR 1 Indicator: Is the account a one-time account?
XZEMP XZEMP CHAR 1 Indicator: Alternative payee in document allowed ?
VBUND RASSC CHAR 6 Company ID of Trading Partner
FISKN FISKN_K CHAR 10 Account number of the master record with fiscal address
STCEG STCEG CHAR 20 VAT registration number
STKZN STKZN CHAR 1 Natural Person
SPERQ QSPERRFKT CHAR 2 Function That Will Be Blocked
GBORT GBORT_Q CHAR 25 Place of birth of the person subject to withholding tax
GBDAT GBDAT_Q DATS 8 Date of birth of the person subject to withholding tax
SEXKZ SEXKZ CHAR 1 Key for the *** of the Person Subject to Withholding Tax
KRAUS KRAUS_CM CHAR 11 Credit information number
REVDB REVDB_CM DATS 8 Last review (external)
QSSYS QSSYS_IST CHAR 4 Vendor's QM system
KTOCK KTOCK CHAR 4 Reference Account Group for One-Time Account (Vendor)
PFORT PFORT_GP CHAR 35 PO Box city
WERKS WERKS_EXT CHAR 4 Plant (Own or External)
LTSNA LTSNA CHAR 1 Indicator: vendor sub-range relevant
WERKR WERKR CHAR 1 Indicator: plant level relevant
PLKAL FABKL CHAR 2 Factory calendar key
DUEFL DUEFL_BKPF CHAR 1 Status of Data Transfer into Subsequent Release
TXJCD TXJCD CHAR 15 Jurisdiction for Tax Calculation - Tax Jurisdiction Code
SPERZ SPERZ CHAR 1 Payment Block
SCACD SCACD CHAR 4 Standard carrier access code
SFRGR SFRGR CHAR 4 Forwarding agent freight group
LZONE LZONE CHAR 10 Transportation zone to or from which the goods are delivered
XLFZA XLFZA CHAR 1 Indicator: Alternative payee using account number
DLGRP DLGRP CHAR 4 Service agent procedure group
FITYP J_1AFITP_D CHAR 2 Tax type
STCDT J_1ATOID CHAR 2 Tax Number Type
REGSS J_1AREGSS CHAR 1 Registered for Social Insurance
ACTSS J_1AACTSS CHAR 3 Activity Code for Social Insurance
STCD3 STCD3 CHAR 18 Tax Number 3
STCD4 STCD4 CHAR 18 Tax Number 4
IPISP J_1BINDEQU CHAR 1 Tax Split
TAXBS TAXBS NUMC 1 Tax Base in Percentage
PROFS PROFS CHAR 30 Profession
STGDL STGDL CHAR 2 Shipment: statistics group, transportation service agent
EMNFR EMNFR CHAR 10 External manufacturer code name or number
LFURL URL CHAR 132 Uniform resource locator
J_1KFREPRE REPRES CHAR 10 Name of Representative
J_1KFTBUS GESTYP CHAR 30 Type of Business
J_1KFTIND INDTYP CHAR 30 Type of Industry
CONFS CONFS_X CHAR 1 Status of Change Authorization (Central)
UPDAT UPDAT_RF DATS 8 Date on Which the Changes Were Confirmed
UPTIM UPTIM_RF TIMS 6 Time of Last Change Confirmation
NODEL NODEL_X CHAR 1 Central deletion block for master record
QSSYSDAT QQSSYSDAT DATS 8 Validity date of certification
PODKZB PODKZB CHAR 1 Vendor indicator relevant for proof of delivery
FISKU FISKU CHAR 10 Account Number of Master Record of Tax Office Responsible
STENR STENR CHAR 18 Tax Number at Responsible Tax Authority
.APPEND ALFA1_PSO STRU 0 Local Authority Additional Fields (Address)
PSOFG PSOFG CHAR 10 Processor group
PSOIS PSOIS CHAR 20 Subledger acct preprocessing procedure
.INCLUDE IADDR_PSO STRU 0 Local Authority Additional Fields (Address)
PSON1 NAME1_GP CHAR 35 Name 1
PSON2 NAME2_GP CHAR 35 Name 2
PSON3 NAME3_GP CHAR 35 Name 3
PSOVN PSOVN CHAR 35 First name
PSOTL PSOTL CHAR 20 Title
PSOHS PSOHS CHAR 6 House number: is no longer used from Release 4.6B
PSOST PSOST CHAR 28 Street: No longer used from Release 4.6Bhi
u click on the entry help/check
after that some table name r there,just click on the tables that r appeared so theat fileds is key fields for another table,so u may use that as key mandatory fields..in u r program..
not all fields according to u r requirement u sue that fields -
Hi all,
I am doing a BPM for 1:n multimapping.
Start->receive idoc->Transformation->send asynchronous->Stop.
In the transformation, I have a source message and two target messages. I want to send this message as a single message to the receiving MQ system.
In the send asynchronous step after transformation, I can give only one message for sending. Can anyone suggest some solution for this?
Thanks in advance,
DenoHi,
If you follow Siva suggestion you will altering the XSD of the IDoc itself. I feel its better you enclose both messages in a separate root tag.
Also when merging, you should use Message Type XSD of your custom strcuture and not Data Type XSD of your custom structure.
The following is an example of a merged custom XSD and IDoc XSD:
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="MergedMessage">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="resultset" type="resultset" />
<xsd:element name="CREMAS03">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="IDOC" type="CREMAS.CREMAS03"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="CREMAS03">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="IDOC" type="CREMAS.CREMAS03"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:complexType name="CREMAS03.E1LFA1M">
<xsd:annotation>
<xsd:documentation>
Segment for general vendor data
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="MSGFN" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Function
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="3"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="LIFNR" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Account number of vendor or creditor
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ANRED" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Title
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="15"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="BAHNS" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Train station
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="25"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="BBBNR" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
International location number (part 1)
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="7"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="BBSNR" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
International location number (part 2)
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="5"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="BEGRU" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Authorization group
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="4"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="BRSCH" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Industry key
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="4"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="BUBKZ" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Check digit for the international location number
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="1"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="DATLT" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Data communication line no.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="14"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="DTAMS" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Report key for data medium exchange
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="1"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="DTAWS" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Instruction key for data medium exchange
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="2"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ERDAT" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Date on which the Record Was Created
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="8"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ERNAM" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Name of Person who Created the Object
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="12"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ESRNR" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
POR subscriber number
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="11"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="KONZS" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Group key
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="KTOKK" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Vendor account group
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="4"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="KUNNR" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Customer number
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="LAND1" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Country of company
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="3"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="LNRZA" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Account number of vendor or creditor
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="LOEVM" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Central Deletion Flag for Master Record
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="1"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="NAME1" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Employee's last name
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="35"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="NAME2" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Employee's last name
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="35"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="NAME3" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Employee's last name
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="35"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="NAME4" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Employee's last name
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="35"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ORT01" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
City
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="35"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ORT02" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
District
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="35"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="PFACH" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
P.O. Box
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="PSTL2" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Postal Code
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="PSTLZ" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Postal Code
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="REGIO" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Region (State, Province, County)
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="3"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="SORTL" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Character field length = 10
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="SPERR" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Central posting block
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="1"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="SPERM" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Centrally imposed purchasing block
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="1"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="SPRAS" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Language key
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="1"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="STCD1" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Tax number 1
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="16"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="STCD2" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Tax number 2
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="11"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="STKZA" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Indicator: Business Partner Subject to Equalization Tax?
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="1"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="STKZU" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Indicator: Business partner subject to tax on sales/purch. ?
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="1"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="STRAS" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
House number and street
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="35"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="TELBX" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Telebox number
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="15"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="TELF1" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
First telephone number
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="16"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="TELF2" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Second telephone number
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="16"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="TELFX" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Fax number
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="31"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="TELTX" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Teletex number
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="30"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="TELX1" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Telex number
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="30"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="XCPDK" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Indicator: Is the account a one-time account?
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="1"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="XZEMP" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Indicator: Alternative payee in document allowed ?
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="1"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="VBUND" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Company ID of trading partner
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="6"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="FISKN" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Account number of the master record with fiscal address
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="STCEG" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
VAT registration number
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="20"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="STKZN" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Indicator: Is business partner a natural person?
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="1"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="SPERQ" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Function That Will Be Blocked
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="2"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ADRNR" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Address
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="MCOD1" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Search term for matchcode search
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="25"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="MCOD2" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Search term for matchcode search
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="25"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="MCOD3" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Search term for matchcode search
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="25"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="GBORT" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Place of birth of the person subject to withholding tax
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="25"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="GBDAT" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Date of Birth
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="8"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="SEXKZ" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Key for the *** of the Person Subject to Withholding Tax
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="1"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="KRAUS" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Credit information number
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="11"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="REVDB" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Last review (external)
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="8"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="QSSYS" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Vendor's QM system
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="4"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="KTOCK" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Reference Account Group for One-Time Account (Vendor)
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="4"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="PFORT" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
PO Box city
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="35"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="WERKS" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Plant
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="4"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="LTSNA" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Indicator: vendor sub-range relevant
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="1"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="WERKR" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Indicator: plant level relevant
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="1"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="PLKAL" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Factory calendar key
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="2"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="DUEFL" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Status of Data Transfer into Subsequent Release
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="1"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="TXJCD" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Jurisdiction for tax calculation - tax jurisdiction code
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="15"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="SCACD" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Standard carrier access code
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="4"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="SFRGR" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Forwarding agent freight group
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:rest -
Risk Mgmnt COnfiguration steps
Hello Friends
Can anyone please tell me the complete steps to configure "Risk Management " with LoC (Letter of Credit) & what is the necessary data to be collected from the business, for configuring the same.
Regards
Sumanth.GururajHi,
The configuration steps for risk management
How To Do Configuration For Credit Management
Credit and risk management takes place in the credit control area. According to your corporate requirements, you can implement credit management that is centralized, decentralized, or somewhere in between.
An organizational unit that represents the area where customer credit is awarded and monitored. This organizational unit can either be a single or several company codes, if credit control is performed across several company codes. One credit control area contains credit control information for each customer.
For example, if your credit management is centralized, you can define one credit control area for all of your company codes.
If, on the other hand, your credit policy requires decentralized credit management, you can define credit control areas for each company code or each group of company codes.
Credit limits and credit exposure are managed at both credit control area and customer level. You set up credit control areas and other data related to credit management in Customizing for Financial Accounting. The implementation guide is under Enterprise Structure -> Definition or Assignment -> Financial Accounting and then Maintain credit control area. You assign customers to specific credit control areas and specify the appropriate credit limits in the customer master record.
Settings for determining the credit control area of a document. The settings of items 1 - 4 are taken into account according to their priority. The credit control area found is stored in field VBAK-KKBER.
1. Transaction OB38
Check which credit control area is assigned to the company code.
Company code:
Credit control area:
2. Transaction OVFL
Check which credit control area is assigned to the sales area.
Sales area:
Credit control area:
3. Transaction XD02 or VD02
Check which credit control area is assigned to the payer.
Payer:
Credit control area:
4. Transaction SE37
Is user exit EXIT_SAPV45K_001 being used?
5. Transaction OBZK
For the settings under items 2 - 4, field "All company codes" must be marked in Transaction
OB45, or the credit control area must be entered under the relevant company code in table T001CM of the credit control areas allowed.
Company code:
Credit control areas allowed:
6. Settings for the credit checks
7. Transaction OVAK
Which settings do exist for the sales document type used?
Sales document:
Check credit:
Credit group:
8. Transaction OVAD
Which settings do exist for the delivery type used?
Delivery type:
Credit group for delivery:
Credit group for goods issue:
9. Transaction OB01
Credit management/Change risk category
Definition of the risk category for each credit control area. This risk category can be assigned to a credit account by using Transaction FD32.
10. Transaction OVA8
Here, the individual credit checks for key fields
o credit control area
o risk category
o credit group are set. Take these key fields from the above settings and go to the detail screen. In particular, check whether fields "Reaction" and "Status/block" are set correctly. To carry out follow-up actions in case of a credit block, the credit check status must be set (field "Status/block").
11. Transaction FD32
Credit master data for the payer of the relevant document.
Credit account:
Credit limit:
Risk category:
Currency:
12. Settings for updating the credit values Update of the credit values is required for the limit check (static or dynamic credit limit check).
13. Transaction OVA7
Update of the credit value is active for the corresponding item type if the check box is marked. This field corresponds to
field "Active receivable" in Transaction VOV7.
Item type:
Active receivable:
14. Transaction V/08, Pricing
In the pricing procedure used for pricing, subtotal "A" must be entered in a line for determining the credit value (mark the pricing procedure and doubleclick on "Control").
Usually, the net value plus taxes is used. This way the system is determined to use this subtotal for credit pricing. The credit price is stored in field VBAP-CMPRE and used for update and credit check.
You can find the used pricing procedure of the order under "Item -> Condition -> Analysis".
Pricing procedure:
Line with subtotal = 'A':
15. Transaction OB45
Which update group (field "Update") do you use in the relevant credit control area? The default setting is "12". If you use another update group, check whether this is fine with you. If you open an OSS message, please tell us the alternative update group.
Credit control area:
Update:
16. Transaction OMO1
Which kind of update did you choose for structure S066?
In any case, "Synchronous update (1)" has to be chosen as the kind of update. All other settings will lead to errors.
Credit Management Reports
The following table provides an overview of all the reports that are available for credit management:
Program Function
RFDKLI10 Customers with Missing Credit Data
Checks whether the data regarding credit limits is complete and issues relevant error lists. These enable you to maintain the relevant definitions either manually or with batch input.
RFDKLI20 Reset Credit Limit for Customers
Resets the credit limit information in the control areas.
RFDKLI30 Credit Limit Overview
Lists the central and control area data for each customer.
RFDKLI40 Credit Overview
Provides a comprehensive overview of the customeru2019s credit situation.
RFDKLI41 Credit Master Sheet
Displays and prints the customer master data for an individual account that is needed for credit management.
RFDKLI42 Early Warning List
Displays and prints customers in Credit Management who have been listed by the credit check as critical.
RFDKLI50 Credit Limit Data Mass Change
Changes all the credit management master data together.
RFDKLIAB Display Changes to Credit Management
Displays the changes to credit management master data for all accounts.
RVKRED06 Check Blocked Credit Documents
Checks all the documents blocked for credit reasons. The report is started in the background and should run after the incoming payments programs.
RVKRED77 Reorganize SD Credit Data
Reorganizes open credit, delivery and billing values. It can be used in the event of an update error, for example.
RVKRED08 Checking sales documents which reach the credit horizon
Rechecks all sales documents that fall within the credit limit horizon of the dynamic credit limit check. The report is run at regular intervals and should be run at the start of each period. The system uses the current date and the period split for the open order values to propose the u2018next credit check dateu2019.
RVKRED09 Check Credit Documentation Background
Checks released documents whose validity period of the release has been exceeded (number of days).
RVKRED88 Simulating Reorganization of SD Credit Data
To run a report:
1. Choose System ® Services ® Reporting.
2. Enter the name of the report.
3. Choose Program ® Execute.
4. Enter your selection criteria.
5. Choose Program ® Execute or Program ® Execute and print.
SAP SD Credit Management Tcodes
All business have their own credit management needs, SAP allows you to specify your own automatic credit checks based on a variety of criteria. You can also specify at which critical points in the sales and distribution cycle the system carries out these checks.
SM30 - Table/View
u2022 V_TVTW - Define Distribution Channel
u2022 V_TVTA_KKB - Assign sales area to credit control area
u2022 V_T014 - FI - Define Credit Control Area
u2022 T001CM - FI - Assign Permitted Credit Control Area to company code
OVXG - Set up Sales Areas
e.g. Sales Organization
Distribution Channel
Division
Distribution Channel
Division
FD32 - Customer Credit Management
OVAK - Define credit limit check by sales document type
u2022 Check Credit
o A - Credit limit check and warning message
o B - Credit limit check and error message (no sales order can be created)
o C - Credit limit check and delivery block (block delivery if hit credit limit)
Options B and C -> used for checking open order values (when you create/change the sales order)
o D - Automatic credit control with open order values
More control in transaction OVA8 - Automatic credit control
You check for open orders and deliveries, or just open deliveries.
or open order values with other options
u2022 Credit group
o Allows you to combine different sales document types for the credit limit check
VKM1 - Blocked SD Documents - Finance have to released the delivery block
OVAD - Define credit limit check by delivery order
u2022 whether the automatic credit check occurs at the time of delivery creation and/or goods issue
OVA7 - Define credit limit check by item category
u2022 Set whether to include/exclude item category for credit limit check
OVA6 - Define credit group. You can groups together different business transactions which should be dealt with in the same manner with regard to the credit check.
You enter the credit groups when you configure the sales document types for credit management and define the (D - automatic credit check).
u2022 SAP default credit groups
o 01 - credit group for sales order
o 02 - credit group for delivery
o 03 - credit group for goods issue
OVA8 - Automatic credit control - Double click on the line items
You can have the followings credit limit check :-
u2022 Static
Depends on the customer total value of open orders, deliveries, billing documents and open items.
u2022 Open items
No of days open
Overdue open items checks is based on the ratio of open items that are overdue by a certain number of days.
Max open items %
The customer balance must not exceed a certain percentage.
u2022 Oldest open items
If you don't want to deliver to the customer at all when even only 1 invoice is overdue.
Tick the Check for Oldest Open Item and Set the field Days oldest item = 1.
Dayu2019s oldest item
No of days allowed for overdue or payment terms.
Use of the credit checks Oldest Open Item. If a user attempts to alter the order quantity of a released sales document
that was previously blocked, it would be re-blocked again by the system. The system only re-blocks the sales document if the new order quantity is above a certain % amount.
u2022 Released documents are still unchecked
The preset % is whatever you want to set it as when configuring your automatic credit processing. You enter a deviation % and number of days,eg, you can set it so that an order can be changed by up to 10% within 30 days of original order entry date without it going back on credit block.
u2022 Next Review Date
If a customer has a credit limit of 1000 USD, and you would like to restrict this credit limit only to be available in current month (say March). If the document date is in April then the credit limit is zero.
You can use the "NextReview date" and "Number of days" fields and combined it with the "Last int.review" field in customer credit master "Status" view (FD32).
VOKR - Display of work list for credit management (configure the display variant)
SIMPLE CREDIT CHECK:
Tr.Code - FD32
It Considers the Doc.Value + Open Items.
Doc.Value: Sales Order has been saved but not delivered
Open Item: Sales Order has been saved, Delivered, Billed & Transferred to FI, but not received the payment from the customer.
Eg: Customer Credit Limit is Rs.1, 00,000/-
Suppose Doc.Value + Open Item Value is Rs.1,10,000/-
Here credit limit exceeds then system reacts.
Options: A) Warning Message
B) Error Message (Sales Order won't be saved)
C) Error Message with Delivery Block
AUTOMATIC CREDIT CHECK: Give extra credit facilities to the particular customer.
STATIC CREDIT LIMIT DETERMINATION: Checking Group + Risk Category + Credit Control Area.
A) Credit Checking Groups: Types of Checking Groups.
01) Sales
02) Deliveries
03) Goods Issue
At all the above 3 levels orders can be blocked.
B) Risk Category: Based on the risk Categories Company decides how much credit has to give to the customer.
HIGH RISK (0001) : LOW CREDIT
LOW RISK (0002) : MORE CREDIT
MEDIUM RISK(0003): AVERAGE CREDIT
Static Credit Check it checks all these doc value & check with the credit limit
1) Open Doc.Value / Sales Order Value: Which is save but not delivered
2) Open Delivery Doc.Value: Which is delivered but not billed
3) Open Billing Doc.Value: Which is billed but not posted to FI
4) Open Item: Which is transferred to FI but not received from the customer.
DYNAMIC CREDIT CHECK:
1) Open Doc
2) Open Delivery
3) Open Billing
4) Open Items
5) Horizon Period = Eg.3Months
Here the System will not consider the above 1,2,3& 4 values for the last 3 months
Then assign the Sales Doc & Del Documents.
Sales Doc.Type(OR) + credit Check (0) + Credit Group (01)
Credit Limit Check for Delivery Type : Del.Type (LF) + Del Credit
Group (02) + Goods Issue Credit Group (03)
User Exits For Credit Checks And Risk Management
Credit Check
I hope this will resolve your issue
Thanks
Anil Hooda -
Field to indicate 'Blocked' vendor
Hi Gurus,
Which field should i use for the 'Blocked' vendor in LFA1 table.
Actaully my requirement is to add one more column 'Blocked' in the standard search help of the vendor field(LFA1-LIFNR).
Please guide me on this issue.
Regards,
AmitHi,
SPERR---Central posting block
SPERM----Centrally imposed purchasing block
LOEVM----Central Deletion Flag for Master Record
NODEL----Deletion block for master record (company code level)
regards,
Omkaram.
Maybe you are looking for
-
I don't like Apple's algorithm that constantly pushes the same songs at me, so I have a couple of playlists configured for songs I haven't listened to in a month, two months, etc. This has worked fine for years. Since I've gotten my iPhone 4S, howeve
-
Withholding tax and Gross amount determination
Dear all First of all, I would like to underline that before to post in this forum I have read all the documentation (official and not official) related to the Withholding Tax configuration in SAP, but in the end I have some doubts and so I kindly as
-
Acrobat failed to connect to DDE Server - Can't open
I've tried to open Adobe and get the following error message after about 5 min or so: Acrobat failed to connect to a DDE server. I am unable to open files. I read the other posts on this and tried the open with and it didn't work - Any idea's on how
-
Method of fetching Account status and user locked date in Portal.
Hi, Can anyone suggest me the method name in UME API in Sap Ep for fetching User Account Status and Last User Locked Date. Or suggest a related code for it. user database is LDAP. Thanks
-
ICal won't refresh appointments unless i click on each day
Please help! When I enter an appointment on my iPhone and synch to iCal, the appointment doesn't show up in month or week view unless I click on the particular day of the appointment. In other words, the new appointment is actually synched to iCal bu