CONDA Idoc AFS to RETAIL

Hi
Iam working for a retail client. Retail system receives CONDA and INFREC idocs from AFS system both while creating a master data and updating the master data. Is there any way to differentiate the idocs whether its creating a masterdata or updating masterdata within retail system.
regards
prasad

I have checked this issue in our own test system and received the same
result.
Error Message no. MH030
The date is limited by the validity period that has generally
been defined at material level (basic data screens)
In the basic screen data you can see in the tab validity from when
the article was created. When an article is created in MM41 it is
valid from today's date
Valid From      10.01.2008                   Valid to        31.12.9999
The article cannot be listed before this date, creation date of the
article. This is standard system behaviour.

Similar Messages

AFs and Retail connection

Hi
anyone have this experience of AFS and retail connection? can share experience?
thanks

Hello Morris,
I know no case where this has been done. All Companies using AFS and Retail are working on with two system landscapes. Most problems are in MM.
Best Regards,
Markus

AFS-Retail Interface-Pricing Conditon Proces (Sales Condition - INFORECORD)

Hi Experts,
We are working on Integration between AFS and RETAIL systems.
We are facing Issue in Sending Sales conditions (VK13-VKP0) from the AFS side, Transfer over to the Retail side as INFOREORD.
What settings (Configurations) are required in AFS & Retail system ?.
When Sales conditions (VK13) are sent in AFS what is the Message Type to be Used ?.
Any Input is highly appreciated.
Thanks and Regards,
Selvakumar. M

Hello Marat,
Did you meant Pricing Info records. If yes, it need to be maintained at the AFS side. When interfacing the materials from AFS to Retail using BD10, you can use the option 'Send Material in Full' to send the prices also.
The prices can be maintained using the transaction VK11. It can be maintained on the material level and also on SKU level. When interfacing as mentioned before, INFREC and COND_A IDocs will also be generated.
Hope this address your query.
Regards
Sudha

IDoc stricture for AFS

Hi
I imported IDoc /AFS/MATMAS04 structure into IR with all fields. There are few fields with "/" as starting letter. Once I imported into IR, it replaced "/" with "_-" for all fields.
Now ,I am sending IDoc from R/3 and been delivered to Integration server and resulting error because XML file is not well formatted. I looked at XML file and found as below
<E1_J3MAR>
</AFS/SELVE>E<//AFS/SELVE>
</E1J3MAR>
Looks like this is not taking effect of Schema definition. Is there any setting required to convert IDoc into XML with "_-" replaced.
Any Idea?
Thanks
Reddi

The only idea I have, is that you work with XI 3.0 SP9. In that case, apply the latest XI patch.
Regards
Stefan

Sender / Receiver on DEBMAS customer IDOCs mapped from XI

Hello XI experts,
I'm hoping you can help me resolve a question.
In our system, customers are maintained in an AFS ERP system. They are then distributed to MDM, via XI, using DEBMDM messages.
We have a second (Retail) ERP system that also needs the customer data. An XI colleague has created a mapping, so that the DEBMDM IDOC from AFS is mapped to DEBMAS and ADRMAS IDOCs, which are sent to AFS.
Functionally this works fine: the customer data from AFS goes to both MDM and retail as expected.
The question is on the IDOCs arriving in Retail. They have the same logical system for the Sender and Receiver, which is the Retail logical system. So it looks like the IDOCs have been created in Retail and then processed, rather than being created in XI. However in XI, in transaction IDX5, we can see IDOC numbers. I'm a developer with no XI experience, so I may be misunderstanding how XI works.
- Does XI actually create an IDOC locally and then send it out?
- Or would XI be calling some kind of RFC in my Retail system to build the IDOC there?
- If the IDOC is built locally, can anyone suggest why I am getting the sending partner to be the same as the receiver?
Even if the sending and receiving systems are set in the XI mapping, the values still get overwritten with the Retail logical system.
Many thanks, Roger

Roger,
In the Receiver IDoc Adapter , 3 options are available.
Apply Cntrol Record Values From payload.
When you select this option, the values of these fields are filledfrom the idoc payload,
+MESCOD
· MESCFT
· TEST
· EXPRSS
· STD
· STDVRS
· STDMES
· SNDSAD
· SNDLAD
· RCVSAD
· RCVLAD
· REFINT
· REFGRP
· REFMES
· STATUS
· DIRECT
· OUTMOD
· CREDAT
· CRETIM+
Take Sender From Payload
Selecting this fills the values for Sender System with values of SNDPRN and SNDPRT.
Take receiver from payload
Receiver Partner Names values are filled from the payload with values of RCVPRN and RCVPRT.
These are the only values from which you can pass the value from payload, rest of the fields are filled by default.
More,
http://help.sap.com/saphelp_nw2004s/helpdata/en/13/95244269625633e10000000a155106/content.htm
Regards
Bhavesh

Enhancement and new features available in AFS 6.0 in reference to AFS 5.0?

Hi Experts,
Please can you explain what are the Enhancement and new features available in AFS 6.0 in reference to AFS 5.0

Hi Mithun,
Following are the details you needed.
Enhancement and new features available in AFS 6.0 wrt AFS 5.0
AFS Interface
AFS GTS Master Data Integration - IS-AFS-INT-GTS (New)
As of SAP AFS 6.0, you can integrate the SAP Global Trade Services 7.1 (SAP GTS 7.1) master data to the AFS data.
AFS Retail Integration (Change)
As of SAP AFS 6.0, the integration of Apparel and Footwear Solution (AFS) with Retail has been
Enhanced by the following functions:
u2022     One SAP Retail Logical system is mapped to multiple Customers in SAP AFS system, which ensures that each Customer can be mapped to a different purchase organization.
u2022     You can maintain the retail merchandise category in the AFS material master for each retail logical system.
u2022     The variant numbers created in the retail for the article (material in AFS) have the number with the category and grid combination. A new BADI method is used to allow the user to change the variant numbering as required.
u2022     The material type of the generic article created is the same as the AFS material. A new BADI method is used to set the material type of the article as required.
Quality Management (IS-AFS-QM)
Enabling QM for Goods Receipt (GR) Process for AFS (New)
As of SAP AFS 6.0, you can activate the inspection type at material level and control the inspection lot creation at stock keeping unit (SKU) level during the goods receipt process.
Additionally, during posting of quality inspection stocks, you can directly post stock of one SKU to unrestricted stock of another SKU.
Basic Data (IS-AFS-BD)
Commodity Codes at the SKU Level (New)
As of SAP AFS 6.0, you can maintain commodity codes at the SKU level in the material master. A new relevancy Global Trade Services (GTS) is allotted to the characteristics attached to the grid and categories. If this new relevancy is set then the commodity codes can be assigned at the SKU level. You can also assign commodity codes of different countries other than the country in which the plant is located.
The AFS material master IDoc and BAPI have been enhanced to handle commodity codes at the SKU level.
Material Master Enhancements (New)
As of SAP AFS 6.0, the following enhancements have been made in the material master:
u2022     You can maintain commodity codes at the stock keeping unit (SKU) level.
u2022     You can maintain the retail data merchandise category and characteristic profile at the material master level. This is used to create article in retail.
u2022     You can maintain quality management (QM) inspection type at SKU level.
u2022     You can enable Seasons for inventory management (IM).
Materials Management (IS-AFS-MM)
Seasonality Roundoff - Inventory Management-(New)
As of SAP AFS 6.0, season functionality is extended to Inventory Management (IM). This enables you to gain an overview of material movements during each season. You can maintain stocks for different seasons separately. To enable this functionality, you have to activate the Season Active in IM indicator for a material in the material master. This indicator can be set only for materials created in AFS 6.0. If the season is maintained for an SKU in the material master, you can obtain season information for the SKUs in batches, in material movement documents and in stock tables.
Also, as of AFS 6.0, you cannot set the Season Fixed indicator for new materials. However, for old materials (materials created in AFS 5.0 with Season Fixed indicator) the behavior remains the same.
Stock Selection Available in Transaction MIGO (New)
As of SAP AFS 6.0, the goods movement transaction MIGO has been enhanced with Stock Selection for AFS materials. Goods movement here implies only goods issued/transfer postings without document reference.
Consumption of PIRs by TPO, MTO and PTO (New)
As of SAP AFS 6.0, the Consume PIR Customizing indicator at sales and distribution (SD) item category level enables special orders like TPO (third-party order), MTO (make-to order) and PTO (purchase-to order) to consume normal planned independent requirements (PIRs).
IS-AFS-MM-PUR Purchasing
Purchasing BAPIs (Change)
The interface of the purchase order (PO) BAPIs mentioned below have been enhanced with optional parameters to handle the AFS data.
Purchase order BAPIs
u2022      AFSPurchaseOrder.GetDetail1 (BAPI_PO_GETDETAIL1)
u2022     AFSPurchaseOrder.Change (BAPI_PO_CHANGE)
u2022     AFSPurchaseOrder.CreateFromData1 (BAPI_PO_CREATE1)
Purchase Requisition BAPIs
u2022     PurchaseRequisition.CreateFromData (BAPI_REQUISITION_CREATE)
u2022     PurchaseRequisition.Change (BAPI_REQUISITION_CHANGE)
u2022     PurchaseRequisition.Delete (BAPI_REQUISITION_DELETE)
Contract BAPIs
u2022     PurchasingContract.Change (BAPI_CONTRACT_CHANGE)
u2022     PurchasingContract.Create (BAPI_CONTRACT_CREATE)
u2022     PurchasingContract.GetDetail (BAPI_CONTRACT_GETDETAIL)
Production planning and control IS-AFS- PP
Manufacturing (IS-AFS-PP-MAN)
BAPI for Bill of Material (BOM) Maintenance (New)
As of SAP AFS 6.0, you use this BAPI (AFSMaterialBOM.AFSMatBomMaintain) to maintain a material BOM. You can also use this BAPI for the following functionalities:
u2022     Creating a standard or AFS BOM
u2022     Changing a standard or AFS BOM
u2022     Updating a quantity distribution profile for AFS BOM components
u2022     Maintaining SKU deviation quantities or zero quantities (if relevant) for AFS BOM components
u2022     Maintaining categories (if relevant) for AFS BOM components
Transaction for Grouping PO using Combined Order Number (New)
BAPIs for AFS Planned Orders - Create, Change and Get Details (Change)
BAPI for Production Orders - Create, Change and Get Details (Change)
Production Planning (IS-AFS-PP-PPL)
Consumption of PIRs by TPO, MTO and PTO (New)
As of SAP AFS 6.0, the Consume PIR Customizing indicator at sales and distribution (SD) item category level enables special orders like TPO (third-party order), MTO (make-to order) and PTO (purchase-to order) to consume normal planned independent requirements (PIRs).
Sales and Distribution (IS-AFS-SD)
BADI for Contract Selection (New)
As of SAP AFS 6.0, you can use this BADI to filter contracts for display when a sales order is created without giving reference to the contract, and when there are open contracts for the material. This functionality is also available for the sales order created by IDocs.
BAPI for AFS Material Availability (New)
you can use this BAPI method MaterialAFS.AFSAvailabilityCheck (/AFS/BAPI_MAT_AVAILABILITY) to determine the available quantity for an AFS material in a certain plant according to ATP (available-to-promise) logic.
Consumption of PIRs by TPO, MTO and PTO (New)
As of SAP AFS 6.0, the Consume PIR Customizing indicator at sales and distribution (SD) item category level enables special orders like TPO (third-party order), MTO (make-to order) and PTO(purchase-to order) to consume normal planned independent requirements (PIRs).
Display of Allocated Quantities (New)
As of SAP AFS 6.0, you can find the allocated quantity information of the contract in the Contract Reference Overview screen.
BAdIs in Mass Document Change MDC (New)
The following NEW Business Add-Ins (BAdIs) are provided:
u2022     BAdI for adding custom selection fields in MDC (/AFS/MDC_SELECT_CUSTOM_FIELDS) -You use this BAdI to implement your business process-specific logic in selecting data in mass Document Change transaction (/AFS/MDC).
u2022     BAdI for adding custom change fields in MDC (/AFS/MDC_CHANGE_CUSTOM_FIELDS) -You use this BAdI for implementing your business process-specific logic in changing custom fields data in transaction /AFS/MDC.
u2022     BAdI for adding custom fields to the Adjust Update tab in MDC (/AFS/MDC_ADJ_UPD_CUSTOM_FIELDS) you use this BAdI to implement custom processes that are specific to your business scenario.
Condition Table Display (Change)
As of SAP AFS 6.0, in transaction J3A9 it is possible to display condition tables for value-added service(VAS) and multi-store order (MSO) condition types beyond the existing limit of 19 condition tables. The Conditions Info display in transactions J3A4 and J3AN can be viewed in an ALV list.
AFS Sales and Distribution (SD) IDOCS
As of SAP AFS 6.0, the function modules J_4A_IDOC_INPUT_ORDERS and J_4A_IDOC_INPUT_ORDCHG are not supported. The standard function module IDOC_INPUT_ORDERS are used instead J_4A_IDOC_INPUT_ORDERS and standard function module IDOC_INPUT_ORDCHG are used instead of J_4A_IDOC_INPUT_ORDCHG. There is no change in the IDOC type /AFS/ORDERS05 which is presently used to create/change sales orders. Accordingly, you must use inbound process code ORDE for message type ORDERS and inbound process code ORDC for message type ORDCHG.
Supporting the Change of Single Characteristic (New)
As of SAP AFS 6.0, you can use transaction /AFS/MDC, to select sales documents by specifying a single characteristic name and value range in the same ways as you select sales documents by specifying grid value.
Partial Quantity Reductions in Sales Order (New)
As of SAP AFS 6.0, you can find the quantity changes done for a schedule line from the sales order screen itself without navigating to the change logs. This is possible only when you reduce the quantity of a schedule line.
Allocation Run (IS-AFS-ARUN)
Seasonality Roundoff - Allocation Run (New)
As of SAP AFS 6.0, season functionality is available in the allocation run (ARun) to ensure the season information is considered while creating assignments, and to cause deallocation as per the settings in the deallocation rule on change in season information in the future receipts, sales order or while performing goods receipt (GR). This functionality is available only with online ARun.
BAPI for Individual Allocation and/or Deallocation
As of SAP AFS 6.0, you can use the BAPI /AFS/BAPI_INDIVIDUAL_ARUN to handle allocation/deallocation of specified sales order quantities for single or multiple orders. This enables you to make:
u2022     New allocations
u2022     Allocations from a particular storage location/batch number
u2022     Allocations for a quantity less than equal to the requirement quantity
u2022     Deallocations for a quantity less than equal to the requirement quantity
u2022     A total deallocation
Hope it helps.
Regards,
Anirban Roy

POS DM Reversed Transaction not able to generate Idoc

Hi Expert
I am able to generate Idoc to sap retail from pos dm in transaction type 1001(Sales), but no idea how to do configure refund/ Reversed Transaction? Is Reversed Transaction using message type WPUBON/WPUUMS?

Hi Jack,
            To configure task for reversal use following navigation path
Goto Tcode /n/posdw/img
POS Data Warehouse Management -> POS Inbound Processing -> Tasks -> Tasks for Task Groups
Now configure all your relevent task for task group 0009 for Tasks Relevant for Transaction Reversal
For e.g.
Profile type
Task Group
Description
Code
Description
YR01
       0009
    Tasks Relevant for Transaction Reversal
0001
Supply BW Immediately, Non-Aggr., w. Distribution
YR01
       0009
    Tasks Relevant for Transaction Reversal
0002
Sales Audit Performed, Manual Task
YR01
       0009
    Tasks Relevant for Transaction Reversal
0010
Generate IDoc WPUBON
YR01
       0009
    Tasks Relevant for Transaction Reversal
0011
Generate IDoc WPUWBW
YR01
       0009
    Tasks Relevant for Transaction Reversal
0012
Generate IDoc WPUFIB
YR01
       0009
    Tasks Relevant for Transaction Reversal
0013
Generate IDoc WPUTAB
YR01
       0009
    Tasks Relevant for Transaction Reversal
0014
Generate IDoc WPUUMS
YR01
       0009
    Tasks Relevant for Transaction Reversal
0015
Credit Card Settlement
YR01
       0009
    Tasks Relevant for Transaction Reversal
0017
Supply mySAP ERP Inventory Management
YR01
       0009
    Tasks Relevant for Transaction Reversal
0020
Supply SAP Forecasting and Replenishment
YR01
       0009
    Tasks Relevant for Transaction Reversal
2001
Material/Stock
YR01
       0009
    Tasks Relevant for Transaction Reversal
2002
Material/Stock with Taxes and Discounts
YR01
       0009
    Tasks Relevant for Transaction Reversal
2011
Register/Cashier/Department/Means of Payment
YR01
       0009
    Tasks Relevant for Transaction Reversal
2012
Means of Payment
Hope it will help....
Regards
Ajaya Kumar Mishra

Sales Order confirmation through standard IDoc in Background

Hi all,
I want to send Order confirmation throough standard or existing IDoc.
Can you please help me the steps to configure the IDoc
and also the standard program to fill the IDoc with the data and send as background job.
It is also the case for
Invoice
and Shipping
Can you please send me the steps to configure and standard program to fill the IDoc with data.
Hope you would respond me ASAP.
Thanks and Regards,
Shalem.

Hi,
After the sales order has been created, an ORDRSP IDoc is automatically created using message control. This IDoc is sent from the vendor system to the retail system, which means that the outbound IDoc can usually be found in the vendor system and the inbound IDoc in the retail system.
SAP menu -> Tools -> Business Communication -> IDoc Basis -> WE02 > Display IDoc.
Before this you need to complete NACE configuration Part.
If you want to send the IDocs automatically while creating sales order, you can configure it using message control. The process code will be SD10, which is for sales order confirmation (called as EDI 855).
Use NACE transaction to create output/message type with program as RSNASTED and form routine as EDI_PROCESSING and configure the condition record for your partner (profile). Also configure the same in your partner profile.
Hope This Info Helps YOU.
Regards,
Raghav

Problem in value mapping in POSDM configuration!

Hi Experts,
                          I am sending data from POS to POSDM. I hav used standard name spaces like GM store Connectivity, BI and Store Connectivity 2.0. I hav also done settings in ID . Made a File adapter and RFC adapter and RD, ID, SA and RA settings.
Data from Sourse: GMTLogTransaction_out is going to the RFC :/POSDW/CREATE_TRANSACTIONS_EXT .
So I hope users can Understand I hav used standard mapping.
Now the issue is in the source structure a perticular field called TENDER ID is mapped with Target Field :Tender Code.
But there is a value mapping in between.
The name of the source Agency is IXREtailPOSLogRetailTransactionTenderID and schema is IXRetailPOSLogRetailTransactionTenderIDSchema and
The name of the Target Agency is POSDWTENDERTYPECODE and schema is POSDWTENDERTYPECODESCHEMA.
    And the Value mapping Context is : http://sap.com/xi/XI.
The problem is I can see this , but I cant assign any value as it is in disabled mode in Messege mapping.
Again In the ID I cannot see this Value mapping , which I expected to see and maniputale.
   experts, please tell me hw to I use this manipulate / incert some values so taht the input when 01 becomes 3101 at output.
If any doubts/ querioes, pls revert back.Please note , I am using all standard components in IR.
Regards,
Arnab .

Hi Arnab / Abhijith,
I am also going to work on the similar kind of requirement which u guys have worked.
Pos( third Party)->PI>POSDM-->IS-Retail ( Inbound)
IS-Retail-> PI->POS( third Party) ( Outbound)
Appreciate if you could help me with some clarifications..
1) What transactions we can update to POSDM..?
2) Does we need to POST all POS transactions first to POS DM and then IS-Retail ( Inbound).?
If that is the case, once transactions posted in POSDM, does we need to do any settings to post idocs automatically to Retail system .. (OR) do we need to develop interface again from POSDM>PI>IS-Retail.( please clarify).
Please suggest .. is it feasable to post only Non aggregated data directly to POSDM and Aggregated Sales ,FI , GRNs to directly to ECC.( Based on client requirement ).
Awaiting for your suggestions.. Please suggest the best appraoch
Thanks & Regards,
Suman

One source File should be sent to Receivers based on Message type

Hi All,
I am facing with a problem, the scenario is File to IDOC...
The file which comes has different message types if Message type is VERIFY then IDOC _-AFS_-DELVRY03 has to be triggered and if Message type is MIGO101 then IDOC _-AFS_-WMMBID02 has to be triggered,
Source message is same for both the idocs and mapping is different...
SO please any one can suggest how to proceed in Integration Directory configuration...
Thanks and Regards,
sridhar

Hi,
Your query is a little ambiguous.
You say, that the message type can be either VERIFY or MIGO101.
You also say that the source message is same for both the idocs. This is not very clear.
In case, you have the same message type, and VERIFY and MIGO101 are two fields/segments in this message type, then all you need to do is check if these segments exist, in interface determination.
Click the + symbol in the inbound interfaces section.Enter the following:
Condition: MT/VERIFY ex If so, call IMapping which maps message to idoc AFS_-DELVRY03. Inbound interface for this would be idoc AFS_-DELVRY03
Condition: MT/MIGO101 ex If so, call IMapping which maps message to idoc -AFS-WMMBID02. Inbound interface for this would be idoc. -AFS-WMMBID02.
In case you have two different message types(which means you have two different source messages), you could create two different scenarios.
Regards,
Smitha.

WPUWBW01 Performance Problem

I am posting Stock Adjustments IDOCS WPUWBW01 for Retail Sales , even though the IDOC contains 1000 articles (materials) , the Article Doc (Material Doc) gets created with 100 Articles (materials).
Is there any config which is restricting the creation of Documents for 100 articles(materials),
Regards,
Binayak

I am posting Stock Adjustments IDOCS WPUWBW01 for Retail Sales , even though the IDOC contains 1000 articles (materials) , the Article Doc (Material Doc) gets created with 100 Articles (materials).
Is there any config which is restricting the creation of Documents for 100 articles(materials),
Regards,
Binayak

Idoc issue in AFS-Retail.

one of our customers require the following criteria for VAT & Surcharge Calculation:
AS PER SAP
Customer's requirement
TAXABLE AMOUNT
1695.83
TAXABLE AMOUNT
1696.37
VAT-5.50%
93.79
VAT-5.50%
93.30
S/C-10% ON VAT-5.5.%
9.38
S/C-10% ON VAT-5.5.%
9.33
BILL AMOUNT
1799.00
BILL AMOUNT
1799.00
Sales process:
Sales done in third part software then via an XML file billing gets uploaded in SAP by 'Z' transaction.
Which means Release to Accounting is not done after VF01.
They do not do VF01 they directly post their billing in accounting by 'Z' Transaction.
More Details
AFS & Retail= 2 Servers
Interface = Idoc
Third Party software at retail stores.
Issue: When we wrote a new sub-routine in pricing procedure, everything started working good but Idoc processing Failed. When we remove that routine Idoc works fine.
Error thrown by SAP:
We checked the SAP Note 506040 also but could not find any solution. Plz help..
Regards,
Abdul Wahab

Idoc issue solved.
.Thanks for your valuable inputs but the issue was due to the inconsistency in data.
an implicit enhancement was there which was changing few values in some tables but not in all the related tables.
so the above mentioned ERROR came.
But now the data is consistent and no IDOC error is there but while release to accounting( from a Custom program ) still the same old values are sent to accounting.
We are on ECC 6.0 so the note number is not valid for us..
Regards
Abdul Wahab

Reversal of goods movt in IS -Retail on Invoice cancellation in AFS

We are looking to reverse goods mvt in IS -Retail (GIT-101mvt type) on Invoice cancellation in AFS
Can someone help?
Regards
Pratiksha Gangatirkar

The issue is we create GIT in Retail system on invoice creation in AFS(VF01) ,which triggers a IDOC and hits the retail system ,the question is how to create a IDOC from Invoice cancellation process(VF11) and nullify the GIT created for the cancelled invoice in Retail.

AFS-Retail interface about price condition

Hi gurus,
I am configuring the AFS-Retail interface. Everything is fine except the price on Retail side is not updated. The scenario is: when value of sales price condition say PR00 on AFS side is changed from 120 to 130, the value of the purchase condition say PB00 on retail side should be updated by ALE and IDocs. There is a customizing table about PR00->PB00 MAPPING in AFS side. The problem is I can tigger the IDoc sending by change PR00 via VK12, but the outbound IDoc is still about PR00 not the PB00 I expected. I search all the notes and related SAP help docs, there are only general info about this price distribution scenario but not the step by step configuration. Also we successed in other ALE/IDoc scenario, so there is no problem about the configuration on them. We are on AFS 5.0. Anyone familar with AFS-Retail please give me some clues.
Thanks,
Tony

Hi, Dennis:
I am working on a similar situaltion and I came across this post.
If I need to use SAP table A004 and KONP on R3 to get list price to BW.
Do you think there is any standard SAP extractors offered?
I am not sure if all "Axxx" related tables does not contain any SAP related built in extractors.
thank you!!
Sylvia

Create a Sales Order with Reference to Contract using IDoc / LSMW ( AFS )

Hi Gurus,
I need to crate a Sales Order with reference to a Contract. I need to upload Sales Orders with reference to contract via LSMW.
So far, I've been able to create the Sales Order with ref to contract. But, the Sales Order Quantity is not getting deducted from the Original Qty in Referred Contract ( When try to create another Sales Order referring to the same Contract.) When a Sales Order is created manually, this is working fine.
Please tell me if I've missed some parameter which stopping it create the link to exact schedule line ( Sizes level )
The Details of the IDoc which is been created via LSMW are as follows;
Message Type: ORDERS
Basic Type     : /AFS/ORDERS05
Process Code : ORDE / DELO
( Tried with both process codes. But the Identification is the same for both: IDOC_INPUT_ORDERS )
*_In Header;_
Segment : E1EDK02 - IDoc: Document header reference data *
Qualifier : '043' - Vendor Contract Number ( Tried with ' 005' - Customer Contract, but it's not working )
Contract Order is mapped for field BELNR
*_In Item;_
Segment : E1EDP02 - IDoc: Document Item Reference Data *
Qualifier : '043' - Vendor Contract Number ( Tried with ' 005' - Customer Contract, but it's not working )
Contract Order is mapped to field BELNR
Line Item of the Contract is mapped to field ZEILE
I also tried passing the Schedule line of Contract in Segment : E1J3P01 AFS IDoc: Doc.item general data
to following fields;
J_3AETENV
J_3AVGETE
/AFS/UETENR
Still its not getting updated in the VBEP also..
Please help me with regard to this. Points will be awarded for your valuable contribution.
Thanks.

Hi,
This issue is been resolved.
One of my friend helped me with resolving this issue..
Once the below mentioned configurations were done on SPRO, the Sales Order was created with reference to Contract and the Qty was reflected when tried to create a new Order referring the same contract.;
u2022     SPRO --> SD -->Sales --> Sales Documents --> Sales Document Header --> Define Sales Document Types --> Field : Outline agreement message; from blank to u201CBu201D.
u2022     SPRO -->SD -->Sales --> Sales Documents --> Sales Document Header --> Maintain Sales Document Types for AFS --> Field : Outline agreement message; from blank to u201CAu201D

CONDA Idoc AFS to RETAIL

Similar Messages

Maybe you are looking for